BFF
GraphQL and REST backends for frontends: shaping one API per client without leaking it into the domain.
GraphQL and REST backends for frontends: shaping one API per client without leaking it into the domain.
Technology selection and the architect path: the scope, trade-offs and communication the next role expects.
Strategic and tactical design: bounded contexts, aggregates and the model that survives a rewrite.
CQRS and event sourcing: the read/write split, the event log and the consistency it buys.
MVC, clean architecture and hexagonal architecture: the dependency rule and where each boundary pays off.
Service discovery, configuration and API gateways: the operational cost of splitting a system.