Software Architecture and Design covers system design, API design, microservices, event driven patterns, and the trade offs behind each. The goal is to help engineers reason about scale, coupling, and long term maintainability before the codebase forces the answer on them.
A production look at resilience patterns: circuit breakers, bulkheads, retry budgets, and backpressure, plus the flapping and retry storms they cause when misconfigured.
Production-grade Kafka patterns for event-driven systems: idempotent producers, transactional writes, at-least-once consumers, schema evolution, and the error handling that keeps things alive at 3 AM.
When CQRS and event sourcing earn their keep, how to implement them in production, and the consistency, versioning, and projection-rebuild problems nobody warns you about.
How REST, GraphQL, gRPC, and tRPC actually compare in 2025. Real benchmarks, migration paths, and the decision framework I use for picking one (or stacking several).
How to tell when your microservices are hurting more than helping, and how to migrate to a modular monolith without losing what was good about the split.
A practical decision matrix for picking between database-per-service and shared databases in 2025, with migration paths, saga patterns, and the cost numbers that actually move the needle.
Build APIs developers actually enjoy integrating with. Consistent endpoints, clear errors, sensible versioning, and the patterns behind good developer experience.