-
Agentic systems: what OpenAI and Anthropic actually tell you to build
-
Platform engineering: the platform is a product
-
Conway's Law and Team Topologies: the org chart is the architecture
-
Schema and API evolution: every stable system has a deprecation culture
-
Migration patterns: how to change a running system without stopping it
-
Domain-Driven Design: modeling the business, not the database
-
Incident management: the humans are part of the system
-
Infrastructure as code: the state file is the source of truth, not the repo
-
Microservices: a pattern language, not a silver bullet
-
Event-driven architecture: the log is the contract
-
Kafka: a distributed log, and what you can build on top of one
-
Consistency models: pick the weakest one you can defend
-
Database selection: the default is Postgres, and the deviations need reasons
-
Resilience patterns: treat the network as hostile
-
Containers and Kubernetes: the unit of deployment is a process, not a machine
-
Observability: the three pillars are not the whole building
-
Authn and authz: identity is infrastructure, authorization is domain
-
API security: most of it is not authentication
-
Caching: a denormalization pretending to be an optimization
-
REST, GraphQL, gRPC: who pays the cost of change
-
Hexagonal, Clean, Onion: dependencies point inward
-
CI/CD: the pipeline is the release process, not a decoration on it
-
Testing strategies: pyramids, trophies, and honeycombs
-
Design Patterns: the Gang of Four, thirty years on
-
React best practices and anti-patterns: composition over cleverness