Hermes Wiki
Synthesis/architecture-fundamentals-new-batch-grounded-in-certexams-and-localz

Synthesis: The New Architecture Fundamentals Batch Is Already Live in Both CertExams and Localz — Just Not Cross-Linked

The connection

Synthesis/architecture-fundamentals-grounded-in-toolstack (2026-07-22) found the first Architecture/Fundamentals batch (caching-strategies, three-pillars-of-observability) mapped onto Mihir's existing Tools/ hands-on notes. This window's second batch — Architecture/Fundamentals/rate-limiting-algorithms, Architecture/Fundamentals/autoscaling-strategies, Architecture/Fundamentals/database-sharding-strategies, Architecture/Fundamentals/encryption-at-rest-in-transit-in-use — extends the same pattern, but the concrete grounding this time is stronger and comes from two other places at once: the SAA-C03 cert material Mihir is actively studying, and the Localz project's own stack documents.

  • Rate limiting: the Fundamentals note recommends token bucket as the default and flags that distributed rate limiting needs a shared store (Redis) or per-instance limiters silently multiply the real limit. CertExams/SAA-C03/Domain1/D1_defense_in_depth.md and Questions/FlashCardsQuestions.md (Card 12) cover the AWS WAF rate-based-rule equivalent of the same concept. Separately, Projects/Localz.md §6 specifies "~20 msg/min per user" rate limiting via Redis as a Phase-0 security must-have, and §5 lists Redis (ElastiCache) as "mandatory even at MVP" for exactly this purpose — Localz isn't a hypothetical example, it's the same design decision the Fundamentals note describes, already committed to in a real project's stack docs.
  • Database sharding: the note's geo/tenant sharding section ("common in multi-tenant SaaS... doubles as a data-residency and blast-radius control") is precisely Localz's own future-scaling shape — Localz-Strategy-and-Architecture-Note.md frames multi-city expansion as a named risk/roadmap item, and the NFR section explicitly calls out "handle growth across multiple cities" with no sharding strategy yet named. This is a live gap the new Fundamentals note directly answers.
  • Encryption at rest/in transit/in use: Localz's NFRs list "encrypted payments, secure document storage" — exactly the at-rest/in-transit split the Fundamentals note insists be treated as two separate claims, not one checkbox. Localz's stack already names AWS Secrets Manager, S3 pre-signed URLs, and TLS-everywhere (via CloudFront/ALB) — the at-rest/in-transit coverage is implicitly there in the stack docs, but "in use" (the third state) isn't discussed anywhere in Projects/Localz.md, which is expected at this stage (no untrusted-infrastructure-operator threat model yet) but worth naming explicitly rather than leaving unstated.
  • Autoscaling: the note's cost-vs-responsiveness framing (reactive scaling's cold-start lag vs. predictive/scheduled) maps onto Localz's EKS/Cluster-Autoscaler/HPA-VPA plans (Tech-Stack.md, deferred to the AWS phase) — not yet a live decision, but the vocabulary the Fundamentals note provides is exactly what that future decision will need.

Why this matters

This is the same observation as the 2026-07-22 synthesis — Architecture/Fundamentals notes and Mihir's own project work aren't cross-linked — but the grounding is more load-bearing this time because Localz isn't a "tools I've used" inventory, it's an active project whose stack docs already contain unresolved gaps (no named sharding strategy for multi-city growth, NFRs with no numeric targets per Localz.md §9E) that these exact Fundamentals notes are positioned to close. The CertExams material adds a second reinforcement loop: Mihir is studying the AWS-specific implementation of the same vendor-neutral concepts he's writing up in Architecture/Fundamentals, for a certification exam that maps directly onto services Localz's own stack docs already name (ElastiCache, RDS/Aurora, WAF).

Concrete next step (hand-curation, not a routine task): a short cross-reference from Architecture/Fundamentals/database-sharding-strategies.md and rate-limiting-algorithms.md to Projects/Localz.md's relevant sections would turn two abstract theory notes into directly actionable design input for a project with a real, currently-unresolved gap.

Hermes Wiki