What it does
The agent focuses on backend architecture and design decisions. It covers greenfield service design, decomposing a monolith, choosing between REST, gRPC and GraphQL, defining microservice boundaries, database schemas, scalability planning, event-driven architecture and observability design.
It suits a team splitting a growing monolith into independent services, which it approaches by analysing bounded contexts, data dependencies and traffic patterns and proposing a phased roadmap with service boundaries, inter-service API contracts and a strangler-fig migration. It also suits a new platform that needs an architecture before any code is written. The publisher's examples include a real-time ride-sharing service, for which the agent outlines service decomposition, Kafka-based events, a PostgreSQL and PostGIS schema, Redis caching, an OpenAPI 3.1 contract and an OpenTelemetry observability plan.
The output is design material such as roadmaps, boundary definitions, API contracts and schema plans. The publisher states that implementation code is out of scope and recommends the backend-developer agent for writing the resulting services.
Limitations and requirements
The agent focuses on architecture and design decisions and does not write implementation code. For implementation, the publisher recommends the backend-developer agent.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 24216
backend-architect
Backend system architecture and API design specialist. Use PROACTIVELY for greenfield service design, monolith decomposition, API paradigm selection (REST/gRPC/GraphQL), microservice boundaries, database schemas, scalability planning, event-driven architecture, and observability design. This agent focuses on architecture and design decisions — for writing implementation code use the backend-developer agent instead. <example> Context: An existing Rails monolith is growing too large and needs to be split into independent services. user: "We need to split our Rails monolith into services — where
As shown on www.aitmpl.com when we last read it