backend-architect

To design scalable backend architecture, define bounded contexts for microservices, establish contract-first API design, and implement resilience patterns like circuit breakers alongside observability metrics for deployment readiness.

Contract-first API design defines interface contracts before implementation, ensuring clear boundaries for REST, GraphQL, or gRPC. It is needed when planning distributed systems to maintain interoperability across separate teams and services.

Define microservice boundaries by establishing bounded contexts within your domain. Inter-service communication is then structured using REST, gRPC, or event-driven interfaces to ensure maintainable and decoupled distributed systems.

Add resilience patterns like circuit breakers, retries, and timeouts to backend systems, while implementing observability through comprehensive logging, metrics, tracing, and health checks to maintain operational stability.

Yes, you can generate architecture documentation including ADRs, runbooks, and architecture diagrams to ensure maintainable backend systems with clearly defined boundaries and deployment readiness.

Yes, the backend architecture approach supports event-driven architecture and WebSocket API design, alongside REST and gRPC, to define scalable interfaces and inter-service communication across distributed domains.