Repository navigation
Define Grafana Cloud, Redis carts, Cloudflare security and Kafka opportunities - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Record the selected Grafana Cloud observability stack, Cloudflare security edge and dedicated Redis Cart service. The owner confirmed a seven-day cart TTL after successful changes; reads do not renew it. Domain name and frontend CDN provider remain undecided.
Add official-source research and architecture diagrams for managed Prometheus/Mimir metrics, Loki logs, Tempo traces, Pyroscope profiles, Faro, OpenTelemetry/Alloy and Graphite support. Cloudflare is selected for DDoS/WAF/Tunnel, with plan-dependent controls and origin restrictions; security selection does not choose frontend hosting, R2 or a CDN migration.
Document Cart ownership, guest/account isolation, API proposal, concurrency/TTL, migration and checkout handoff. Assess Kafka placements, prioritizing Order-created events through a transactional outbox, then future Product image work and catalog projections. Delivery guarantees, consumer idempotency, revision-safe cleanup, retries and asynchronous API prerequisites are explicit. These are architecture decisions/proposals; runtime implementations and new dependencies remain future work requiring their own approvals.
Update the READMEs, badges and related frontend/performance/Kubernetes documentation for consistency. Preserve the educational mock-store scope.
Validation: Prettier and Git whitespace checks passed; Zensical builds without issues. Pre-commit was attempted but platform has no root hook configuration. Existing backend/security/fixture CI runs on this PR. No services or cloud resources were started. Owner authorized review and merge after checks.