brokle-backend-dev

Structure your service with domain-driven design by organizing repository, service, and handler layers within a domain package. Use mandatory domain aliases, implement standardized error handling across all layers, and wire components through the DI container to ensure consistency with Brokle's scalable monolith architecture.

Implement industrial-grade error handling consistently across repository, service, and handler layers. Capture domain errors at the repository level, propagate them through the service layer with context, and translate them to HTTP responses in handlers. This standardized approach prevents inconsistent error reporting across your API.

Use dual authentication patterns: API keys for SDK routes and JWT tokens for dashboard routes. Implement these as middleware components wired through the DI container, ensuring your handlers validate credentials before processing requests according to the route's intended consumer.

Yes. Brokle's architecture supports both server and worker binaries from a single monolith. Share domain logic, repositories, and services between them through the DI container while maintaining separate entry points and message-handling patterns for asynchronous worker tasks.

The Brokle backend uses PostgreSQL for transactional data, ClickHouse for analytics, and Redis for caching. Implement repositories as abstraction layers for each database, wire them through dependency injection, and use standardized error handling to manage database-specific failures consistently.

Follow the provided templates for repository, service, and handler layers within your domain package. Apply mandatory domain aliases and error handling patterns, wire components through the DI container, and reference quick development commands for testing and database operations to accelerate your workflow.