Every component is green, therefore the service works
A team aggregates component health checks into availability while accepted work never reaches its terminal state.
Read →Anti-patterns
Anti-patterns
Choose an area, expand a group or search a topic. Newest materials come first within each group.
Matching articles: 11
No matching articles. Try another term or area.
Resilience and recovery (3)
A backup nobody has restored
A green backup report does not prove the entire service can return within its recovery target.
Read →One resource pool for every dependency
A slow reporting service consumes shared workers and prevents orders from completing.
Read →Analysis and decisions (2)
It is SaaS, so the provider architecture is none of our concern
An API and SLA do not resolve data, IAM, continuity, operations and exit questions.
Read →A temporary file integration without an exit decision
A quick integration becomes the target architecture when no owner, contract or migration trigger is recorded.
Read →Integration and APIs (3)
Compatible because the generator reported no error
A team treats an additive schema change as safe without running supported consumers or checking contract behaviour.
Read →A notification decides the order outcome
Failure of an auxiliary email makes a successfully committed order look failed and encourages the user to create a duplicate.
Read →The distributed monolith
Services share a database and deploy together, adding network costs without independent change.
Read →Security (1)
Authorisation checked at the entrance
The gateway validates a token, while downstream layers assume that an authenticated user may access any referenced resource.
Read →Data and migrations (2)
One-step schema migration
Code, data backfill and removal of the old contract ship together, preventing version coexistence and leaving rollback with an incompatible schema.
Read →A shared database as an integration shortcut
Direct access turns internal tables into an unversioned API and bypasses the data owner’s rules.
Read →