Big Ball of Mud
Uncontrolled dependencies and unclear boundaries.
EAOS · Knowledge
Fehlentwicklungen erkennen, begründen und systematisch korrigieren.
Uncontrolled dependencies and unclear boundaries.
Services deploy separately but must change together.
Independent services bypass ownership through one schema.
Excessive fine-grained network calls.
One service owns unrelated capabilities.
Business logic lives outside domain objects.
Business processes reduced to generic data operations.
Modules depend on each other in loops.
One technology is forced onto every problem.
Technology choice follows novelty rather than need.
Unbounded retries amplify an outage.
Calls wait without a defined bound.
Caching is applied without consistency design.
A simple domain is split too early.
Complexity is added without evidence.
Event consumers form a fragile synchronous path.
Events lack ownership and semantic discipline.
Payloads evolve without contracts.
Database and broker are updated independently.
A failing message is retried forever.
Protection relies on secrecy of implementation.
A workload has broader access than required.
Credentials are stored in source or images.
Large mutable state is embedded in tokens.
Tenant data separation is implicit or incomplete.
Auditability is added too late.
Personal data is copied without control.
Temporary waivers never expire.
Controls are marked complete without evidence.
A risk exists without an accountable owner.
Each environment is manually unique.
Runtime changes bypass version control.
Too many low-value alerts obscure incidents.
Dashboards exist without users or actions.
Logs replace purposeful telemetry design.
Backups exist but recovery is untested.
Critical continuity depends on one location.
Servers are manually maintained as unique assets.
Orchestration is adopted without workload need.
Sidecars create hidden resource and lifecycle cost.
Data accumulates without quality and ownership.
Uncontrolled copies cause inconsistency and exposure.
All workloads are forced into one shared store.
Analytical load impacts operational systems.
Schema changes lack ordered, repeatable evolution.
AI is deployed without reproducible quality tests.
Prompt logic is duplicated and unmanaged.
An agent has excessive tools and autonomy.
Generation is added before retrieval is validated.
Model output is treated as unquestionable fact.
Layer Cake creates avoidable architecture risk.
Interface Explosion creates avoidable architecture risk.
Abstraction without Need creates avoidable architecture risk.
Mega Module creates avoidable architecture risk.
Hidden Coupling creates avoidable architecture risk.
Architecture by Diagram Only creates avoidable architecture risk.
Framework-Coupled Domain creates avoidable architecture risk.
Package by Technical Layer Only creates avoidable architecture risk.
Orphan Module creates avoidable architecture risk.
Versioned Copy Architecture creates avoidable architecture risk.
Point-to-Point Spaghetti creates avoidable integration risk.
ESB as Business Brain creates avoidable integration risk.
Shared Event Topic creates avoidable integration risk.
Consumer-Specific Event creates avoidable integration risk.
Breaking Contract Release creates avoidable integration risk.
Polling Everywhere creates avoidable integration risk.
Webhook without Retry creates avoidable integration risk.
Unbounded Payload creates avoidable integration risk.
RPC over Kafka creates avoidable integration risk.
No Idempotency creates avoidable integration risk.
Long-Lived Feature Branch creates avoidable delivery risk.
Manual Gatekeeping creates avoidable delivery risk.
Pipeline Snowflake creates avoidable delivery risk.
Environment Drift creates avoidable delivery risk.
Release Train Bottleneck creates avoidable delivery risk.
Config in Image creates avoidable delivery risk.
Test Later creates avoidable delivery risk.
Always Green Dashboard creates avoidable delivery risk.
Rollback by Hope creates avoidable delivery risk.
Unreviewed Hotfix creates avoidable delivery risk.
Architecture Police creates avoidable governance risk.
Committee Bottleneck creates avoidable governance risk.
Document and Forget creates avoidable governance risk.
Metric Gaming creates avoidable governance risk.
Policy without Remediation creates avoidable governance risk.
Tool-First Governance creates avoidable governance risk.
Ownership by Assumption creates avoidable governance risk.
Review without Evidence creates avoidable governance risk.
Roadmap without Capacity creates avoidable governance risk.
Decision without Consequences creates avoidable governance risk.
N+1 Query creates avoidable performance risk.
Unbounded Queue creates avoidable performance risk.
Thread per Everything creates avoidable performance risk.
No Backpressure creates avoidable performance risk.
Huge Batch creates avoidable performance risk.
Tiny Batch creates avoidable performance risk.
Global Lock creates avoidable performance risk.
Synchronous Fan-Out creates avoidable performance risk.
Unbounded Cardinality creates avoidable performance risk.
Load Test in Production Only creates avoidable performance risk.
Suchbegriff oder Filter anpassen.