Zero Trust Between Services: Service-to-Service Authentication in Practice
Internal networks earn no default trust. mTLS, service JWTs, and workload identity in real environments.
Topic guide
System architecture in practice: monolith or microservices, database scaling, caching, zero-downtime migrations, and distributed systems.
3 topics · 17 articles
When to split your system and when to keep it together.
Internal networks earn no default trust. mTLS, service JWTs, and workload identity in real environments.
Naive chunking returns garbage. Full pipeline: semantic chunking, embeddings, hybrid search, and reranking.
Cascade layers end the specificity wars; container queries let the card measure its own container. A migration path without rewriting your CSS.
The five principles, the code pattern that violates each one, and the version that fixes it. Where SOLID pays off in a project and where it turns into useless layering.
Five patterns that show up in production, implemented in TypeScript: Repository, Strategy, Observer, Decorator, and Builder. Plus the line where none of them is worth adding.
Monorepos solve code sharing and atomic refactors, and charge for tooling setup and boundary discipline. Adoption criteria, Turborepo versus Nx, and a folder structure that holds up.
Scaling data: replicas, caching, migrations, and multi-tenancy.
ALTER TABLE freezes production. Expand-contract splits schema changes into phases compatible with coexisting versions.
A tenant_id column, schema-per-tenant, or database-per-tenant? Costs, risks, and when to migrate between the three.
Caching takes ten lines of code. Deciding what goes in, when it expires, and who deletes it takes the rest of the project. Strategies with Redis, CDN headers, and cache warming, with code.
Token bucket, fixed window, and sliding log solve different problems. Key by IP, user, or API key, headers the client reads, and per-route limits. Code with Redis and express-rate-limit.
An honest EXPLAIN ANALYZE reveals the two-million-row scan. A guide to B-tree, GIN for JSONB, partial and covering indexes in production PostgreSQL.
Consistency, availability, and communication between services.
A backup without a tested restore is superstition. Defined RPO/RTO, 3-2-1 strategy, scheduled disaster simulation.
Google Docs ruined the baseline: users expect simultaneous conflict-free editing. Collaboration architecture explained.
Your messaging choice defines cost and operability. Compared by throughput, ordering, and TCO.
A ramp scenario, a p95 threshold that fails the build, and k6 in CI. Load testing turns latency into a number the team defends and investigates with traces.
Five squads in one repository choke merges and builds. Micro-frontends free the team and charge a price in runtime, deploys, and debugging. Adoption criteria and real costs.
An external provider goes down and your queue bloats. Circuit breaker, retry with jitter, bulkhead, and timeout: the four patterns that cut a failure cascade.
Once the monolith becomes the bottleneck, for deployment, scale, or coordination between teams. That usually shows up around 30 engineers.
Vertical first, because it is simpler. Move to horizontal scaling (sharding) only when a single instance can no longer cope, even with read replicas.
Only if you need a specific NoSQL feature. For most systems, PostgreSQL is more than good enough.
ACID by default. Accept eventual consistency only where horizontal scale requires it, and make that explicit to whoever consumes the data.