| ECO-ARC-ARCH-001 |
Over-provisioned compute |
warning |
Architecture |
| ECO-ARC-ARCH-002 |
Always-on low-traffic service |
warning |
Architecture |
| ECO-ARC-ARCH-003 |
Long synchronous dependency chain |
warning |
Architecture |
| ECO-ARC-ARCH-004 |
No autoscaling policy |
warning |
Architecture |
| ECO-ARC-ARCH-005 |
No resource limits in containers |
warning |
Architecture |
| ECO-ARC-ARCH-006 |
Unbounded message queues |
error |
Architecture |
| ECO-ARC-ARCH-007 |
Batch jobs run too frequently |
warning |
Architecture |
| ECO-ARC-ARCH-008 |
Hot storage used for cold data |
warning |
Architecture |
| ECO-ARC-ARCH-009 |
Duplicate services performing the same work |
warning |
Architecture |
| ECO-ARC-ARCH-010 |
No observability on utilization |
warning |
Architecture |
| ECO-ARC-ARCH-011 |
Excessive replica counts |
warning |
Architecture |
| ECO-ARC-ARCH-012 |
No graceful degradation strategy |
warning |
Architecture |
| ECO-ARC-ARCH-013 |
No caching layer for high-read workloads |
warning |
Architecture |
| ECO-ARC-ARCH-014 |
Stateful services blocking scaling |
warning |
Architecture |
| ECO-ARC-ARCH-015 |
Tight coupling across bounded contexts |
note |
Architecture |
| ECO-ARC-ARCH-016 |
Multi-tenant workloads without isolation |
warning |
Architecture |
| ECO-ARC-ARCH-017 |
Inefficient container image size |
note |
Architecture |
| ECO-ARC-ARCH-018 |
No cold-start optimization |
note |
Architecture |
| ECO-ARC-ARCH-019 |
Overly aggressive autoscaling thresholds |
note |
Architecture |
| ECO-ARC-ARCH-020 |
Underutilized GPU/accelerator resources |
warning |
Architecture |