6 docs tagged with "anti-patterns"

Services making excessive network calls for operations that could be done locally or batched.

Services that call each other synchronously in sequence, creating tight coupling and monolith behavior.

Subtypes must be substitutable for their supertypes without breaking client code. Preserve behavioral contracts.

Services too small to be useful, requiring many inter-service calls and creating excessive complexity.

Every inter-service communication is synchronous, creating blocking dependencies and reducing resilience.

Multiple services accessing the same database directly, creating coupling and preventing independence.