backend-api-design

Structure RPC-style API endpoints using a Controller → Manager → Repository pattern, keeping controllers thin, placing business logic in managers, and routing data access through repositories to enforce separation of concerns.

Standardize API contracts and endpoint naming by applying a disciplined layered architecture pattern that dictates parameter handling, error formats, and response models, ensuring consistency and streamlining cross-team reviews.

Review existing backend API designs by auditing endpoints against organizational design rules, checking that controllers remain thin, managers hold business logic, and repositories handle data access without leaking rules.

Yes, you can design new RPC endpoints and validate contracts using the Controller → Manager → Repository pattern, which enforces testability and prevents duplicated logic by strictly separating request exposure, business logic, and data access.

Backend APIs develop duplicated logic and brittle contracts when teams lack a consistent design pattern, a problem solved by enforcing a standard layered architecture that separates controllers, managers, and repositories.

You should avoid putting business rules in API controllers when adopting a layered architecture, as controllers must remain thin request handlers while managers process business logic and repositories manage data access.