DBRaven

Architecture Structural Diff

Compare two scenarios node-by-node. See exactly which components, failure modes, and connections are shared, removed (−), or added (+) when switching from the left scenario to the right.

Select Scenarios to Diff

left, removals (−)

right, removals (−)

Two-Sided Marketplace PlatformE-Commerce Order Platform
3 removed+6 added21 unchanged

Components

19

Two-Sided Marketplace Platform

21

E-Commerce Order Platform

17 shared2+4

Failure Modes

5

Two-Sided Marketplace Platform

6

E-Commerce Order Platform

4 shared1+2

Connections

0

Two-Sided Marketplace Platform

0

E-Commerce Order Platform

0 shared

Components

17 shared2 left only+4 right only
=
Marketplace Mixedworkload
workload
=
Read-Heavy API Backendworkload
workload
=
Financial Transactionworkload
workload
=
PostgreSQLprimary datastore
data management
=
Elasticsearchsupporting component
application logic
=
Rediscache
acceleration
=
Apache Kafkaevent stream
async processing
=
RabbitMQevent stream
async processing
=
Event Sourcingarchitecture pattern
application logic
=
Saga Patternarchitecture pattern
application logic
=
CQRS (Command Query Responsibility Segregation)architecture pattern
application logic
=
Cache-Asidearchitecture pattern
application logic
=
Transactional Outbox Patternarchitecture pattern
application logic
=
Cascading Failureoperational risk
operational risk
=
Lock Contentionoperational risk
operational risk
=
Thundering Herd (Cache Stampede)operational risk
operational risk
=
Queue Backlog Accumulationoperational risk
operational risk
API Gatewayarchitecture pattern
application logic
Hot Partitionoperational risk
operational risk
+
Rate Limitingarchitecture pattern
application logic
+
Circuit Breakerarchitecture pattern
application logic
+
Deadlockoperational risk
operational risk
+
Partial Service Failureoperational risk
operational risk

Failure Modes

4 shared1 left only+2 right only
=
Cascading Failure0 nodes affected
high
=
Lock Contention0 nodes affected
high
=
Thundering Herd (Cache Stampede)1 nodes affected
high
=
Queue Backlog Accumulation0 nodes affected
high
Hot Partition1 nodes affected
highhigh
+
Deadlock2 nodes affected
highhigh
+
Partial Service Failure0 nodes affected
moderate

Connections

Six-Dimension Assessment

Structural comparison across complexity, risk, scalability, maturity, observability, and generator readiness.

expert complexity, 19 nodes, 0 edges, 5 risks, 2 simulation seeds

Complexity

E-Commerce →

high complexity, 21 nodes, 0 edges, 6 risks, 2 simulation seeds

5 risks (top: high), 5 high/critical, 1 confirmed by simulation

Operational Risk

← Two-Sided

6 risks (top: high), 5 high/critical, 0 confirmed by simulation

4 scaling thresholds, 3 migration paths, 6 advisor scaling signals

Scalability

← Two-Sided

4 scaling thresholds, 3 migration paths, 4 advisor scaling signals

Advisor assessment: Advanced; recommended team: Platform Engineering Team; 15 operational requirements

Operational Maturity

tie

Advisor assessment: Advanced; recommended team: Experienced Backend Team; 15 operational requirements

5 watched metrics, 7 observability recommendations, 2 simulation seeds

Observability

E-Commerce →

4 watched metrics, 6 observability recommendations, 2 simulation seeds

generator relevance documented; topology generation relevance noted; simulation relevance noted; 2 seeds with generator notes

Generator Readiness

depends

generator relevance documented; topology generation relevance noted; simulation relevance noted; 2 seeds with generator notes