Choose Modular Monolith before Microservices
When boundaries are still evolving and one deployment is acceptable.
EAOS · Decisions
Enterprise Decision Catalog
Wiederverwendbare Entscheidungsleitlinien als Ausgangspunkt für konkrete ADRs.
Use Outbox for reliable event publication
When state change and event publication must be atomic.
Prefer PostgreSQL for core transactional data
When relational consistency and mature operations are required.
Adopt OIDC for workforce authentication
When centralized identity and federation are needed.
Use Kubernetes only with platform ownership
When operational complexity can be absorbed by a product team.
Define SLO before scaling
When reliability targets need an explicit business basis.
Version public contracts explicitly
When consumers evolve independently.
Separate tenant data deliberately
When one installation serves multiple organizations.
Use Java 21 as current LTS baseline
When modern concurrency and long support are required.
Choose event-driven integration for temporal decoupling
When producers and consumers should evolve independently.
Keep domain free of framework dependencies
When long-term testability and portability matter.
Use GitOps for declarative runtime control
When auditability and reconciliation are required.
Require expiry for policy exceptions
When temporary risk acceptance must not become permanent.
Store evidence with immutable checksums
When auditability and provenance matter.
Measure retrieval before adding generation
When building a RAG system.
Prefer progressive delivery for high-risk releases
When blast radius should be controlled.
Use database per service only with real autonomy
When independent lifecycle outweighs operational cost.
Adopt data products with named ownership
When decentralizing analytical data.
Use a BFF for materially different clients
When mobile and web require distinct interaction models.
Create ADR for irreversible or costly choices
When future teams need context and consequences.
Keine Treffer
Suchbegriff oder Filter anpassen.