software-engineer

To build production-grade backend services, use a phase-driven workflow covering context analysis, service implementation, cross-cutting concerns, and integration. It applies clean architecture, TDD per endpoint, and strict validation aligned with OpenAPI contracts.

Tenant isolation in REST and gRPC APIs is enforced through constructor-based dependency injection and robust error handling. This approach ensures multi-tenant data separation within backend services while maintaining clean architecture boundaries.

Integrating new backend services into brownfield systems requires shared foundations patterns and phase-based development. The process begins with Phase 1 context analysis and approval, followed by implementing reusable components before writing service-specific code.

Applying structured logging and resilience patterns to middleware happens during Phase 3 of the development workflow. This phase handles cross-cutting concerns, ensuring robust error handling and consistent logging across all API endpoints and repositories.

Yes, OpenAPI contracts are required. The backend service implementation workflow enforces architecture contracts and strict validation aligned with these specifications, ensuring consistent API design and endpoint behavior throughout the TDD process.