Skill Wiki
backend-architecture
Domain plugin for backend / distributed-system architecture corpora. Covers 12-Factor App principles, microservices patterns, and the layer / deployment / scale axes that classify the trade-offs.
Atom counts by kind
| Kind | Count |
|---|---|
| principle | 8 |
| pattern | 6 |
| rule | 4 |
Tag vocabulary
Words a brief might contain that signal this domain.
Retrieval axes
Domain-specific dimensions used by Prime's retrieval scoring.
layer · 10 matches
Which architectural layer the atom addresses — process, data, transport, or operational concerns.
deployment-mode · 8 matches
How the system is deployed and run. "Monolith" atoms differ from "microservices" atoms even when both address the same concern.
scale-class · 9 matches
Expected scale and traffic profile. Patterns that earn their cost at "high-scale" are over-engineering at "small".
Sample atoms
Api Gateway
An API Gateway is a single ingress that fronts the microservice fleet. Clients (web, mobile, partner) talk to one URL; the gateway routes to internal services, fans out parallel calls, aggregates responses, terminates TL…
Circuit Breaker
A service that calls a remote dependency wraps the call in a circuit breaker. After a threshold of failures, the breaker trips OPEN and short-circuits subsequent calls — they fail immediately without hitting the network.…
Cqrs
Command Query Responsibility Segregation. The model that handles writes (commands) is separated from the model(s) that handle reads (queries).…
Database Per Service
Each microservice has a private database. No other service reads or writes that database directly — they go through the owning service's API. The schema is an internal implementation detail, free to evolve.…
Saga
When a business transaction must update data in multiple services, you cannot use a single ACID transaction across them (no distributed XA).…
Service Registry
In a dynamic environment (containers come and go, instances autoscale), service hostnames are not known ahead of time.…
Backing Services Attached
Backing services are URLs in env, not addresses in code. The app does not know if its database is on the same host or across the planet.
Build Release Run
Build → Release → Run are three stages that flow one direction. No mutation in production.
Codebase One Per App
One app, one repo. If you have two apps in one repo, split them. If you have one app in two repos, merge them.
Concurrency Process Model
Scale out, not up. Each process type is a horizontally-scalable share-nothing unit.
Config In Environment
Strict separation of config from code. Config lives in the environment, not the repo.
Dependencies Explicit
Declare every dependency. Isolate at runtime. Never lean on system-wide installs.