docs: refine backend architect operational guidance#536
Open
youngledo wants to merge 1 commit into
Open
Conversation
|
Closing — this is my personal fork (bensl84/agency-agents). The canonical project lives at https://github.com/msitarzewski/agency-agents — please re-open your PR there. Thanks! |
Author
Did you look at the wrong project? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This refines the Backend Architect agent guidance around the responsibilities of designing production-ready backend systems.
The update adds guidance for:
Why
A Backend Architect is responsible for more than choosing databases, defining APIs, and scaling services. In production systems, many backend architecture decisions are about operational correctness: whether APIs can evolve without breaking clients, whether data migrations can ship safely, whether retries and queues fail predictably, and whether incidents can be diagnosed from logs, metrics, and traces.
The existing agent already covers backend fundamentals such as databases, APIs, microservices, cloud infrastructure, security, and performance. This change strengthens the role by making contract governance, migration safety, reliability patterns, and observability explicit parts of the Backend Architect's decision-making process.
It also softens microservices-first and horizontal-scaling-first language. A backend architect should choose the simplest architecture that satisfies current and near-term constraints, then document how the system can evolve when scale, ownership, or deployment independence actually require it.
Testing
Not run; documentation-only change.