Compare Scenarios
Side-by-side comparison with decision path analysis. Every dimension traces back to topology, risk propagation, simulation, and advisor intelligence.
Select Scenarios to Compare
Left Scenario
AI / RAG
Multi-Tenant SaaS
Analytics
Financial Ledger
Read-Heavy
Multi-Tenant SaaS
Write-Heavy
Marketplace
Event-Driven
Financial Ledger
Realtime Collab
Realtime Collab
Financial Ledger
Write-Heavy
AI / RAG
Multi-Tenant SaaS
Event-Driven
Analytics
Read-Heavy
Realtime Collab
Search-Heavy
Event-Driven
Event-Driven
Marketplace
Write-Heavy
Right Scenario
AI / RAG
Multi-Tenant SaaS
Analytics
Financial Ledger
Read-Heavy
Multi-Tenant SaaS
Write-Heavy
Marketplace
Event-Driven
Financial Ledger
Realtime Collab
Realtime Collab
Financial Ledger
Write-Heavy
AI / RAG
Multi-Tenant SaaS
Event-Driven
Analytics
Read-Heavy
Realtime Collab
Search-Heavy
Event-Driven
Event-Driven
Marketplace
Write-Heavy
Topology at a Glance
Architecture Comparison
Read-Heavy SaaS API is both simpler and lower-risk than Healthcare Records Platform
Read-Heavy SaaS API is the simpler architecture. Read-Heavy SaaS API carries lower operational risk. They share 4 component(s). Healthcare Records Platform has 5 unique risk(s); Read-Heavy SaaS API has 1. Read-Heavy SaaS API requires lower team maturity to operate.
19
Nodes
0
Edges
6
Risks
3
Seeds
0
Strengths
6
Adv. Risks
7
Nodes
6
Edges
2
Risks
2
Seeds
5
Strengths
2
Adv. Risks
Comparison Dimensions
Complexity
Healthcare Records Platform
expert complexity, 19 nodes, 0 edges, 6 risks, 3 simulation seeds
Read-Heavy SaaS API
moderate complexity, 7 nodes, 6 edges, 2 risks, 2 simulation seeds
Read-Heavy SaaS API is simpler: moderate operational complexity with 7 topology nodes vs 19 for Healthcare Records Platform.
Operational Risk
Healthcare Records Platform
6 risks (top: high), 4 high/critical, 1 confirmed by simulation
Read-Heavy SaaS API
2 risks (top: high), 2 high/critical, 2 confirmed by simulation
Read-Heavy SaaS API has lower operational risk: weighted severity score 8 vs 20 (2 vs 1 simulation-confirmed).
Scalability
Healthcare Records Platform
4 scaling thresholds, 3 migration paths, 6 advisor scaling signals
Read-Heavy SaaS API
4 scaling thresholds, 2 migration paths, 9 advisor scaling signals
Both scenarios have comparable scaling paths. The best choice depends on your specific growth trajectory. Healthcare Records Platform and Read-Heavy SaaS API offer similar numbers of defined evolution steps.
Operational Maturity
Healthcare Records Platform
Advisor assessment: Advanced; recommended team: Platform Engineering Team; 9 operational requirements
Read-Heavy SaaS API
Advisor assessment: Intermediate; recommended team: Experienced Backend Team; 7 operational requirements
Read-Heavy SaaS API requires lower team maturity (Intermediate) vs Advanced for Healthcare Records Platform.
Observability
Healthcare Records Platform
8 watched metrics, 5 observability recommendations, 3 simulation seeds
Read-Heavy SaaS API
8 watched metrics, 3 observability recommendations, 2 simulation seeds
Read-Heavy SaaS API has lower observability burden: 8 watched metrics vs 8.
Generator Readiness
Healthcare Records Platform
generator relevance documented; topology generation relevance noted; simulation relevance noted; 3 seeds with generator notes
Read-Heavy SaaS API
generator relevance documented; topology generation relevance noted; simulation relevance noted; 2 seeds with generator notes
Healthcare Records Platform has more documented generator readiness signals. Note: this is still preliminary.
Architecture Components
Shared (4)
Only in Healthcare Records Platform (15)
Only in Read-Heavy SaaS API (3)
Operational Risks
Shared (1)
Only in Healthcare Records Platform (5)
Only in Read-Heavy SaaS API (1)
Consistency Guarantees
Neither scenario has a recorded consistency-guarantee claim.
Neither scenario has recorded a consistency-guarantee claim; no guarantee comparison is possible from the data on record.
Tradeoff Summary
Complexity vs Risk
Healthcare Records Platform has expert complexity. Read-Heavy SaaS API has moderate complexity. Simpler systems often carry different (not necessarily fewer) risks.
Healthcare Records Platform
Healthcare Records Platform: 6 risks (top: high), 4 high/critical, 1 confirmed by simulation
Read-Heavy SaaS API
Read-Heavy SaaS API: 2 risks (top: high), 2 high/critical, 2 confirmed by simulation
Scaling Path
Healthcare Records Platform offers 4 defined scaling thresholds. Read-Heavy SaaS API offers 4. More defined paths means clearer evolution steps but also more anticipated growth.
Healthcare Records Platform
4 scaling thresholds, 3 migration paths, 6 advisor scaling signals
Read-Heavy SaaS API
4 scaling thresholds, 2 migration paths, 9 advisor scaling signals
Team Maturity Requirement
Read-Heavy SaaS API can be operated by a less experienced team. Healthcare Records Platform requires deeper operational expertise.
Healthcare Records Platform
Advisor assessment: Advanced; recommended team: Platform Engineering Team; 9 operational requirements
Read-Heavy SaaS API
Advisor assessment: Intermediate; recommended team: Experienced Backend Team; 7 operational requirements
Event-Driven vs Synchronous Processing
Healthcare Records Platform uses event stream infrastructure (Kafka/Kinesis), enabling decoupled async processing. Read-Heavy SaaS API does not, keeping the stack simpler but less decoupled.
Healthcare Records Platform
Event stream: async decoupling, consumer lag risk, higher ops burden
Read-Heavy SaaS API
No event stream: simpler stack, synchronous dependencies
Architecture Strengths vs Risks Balance
The advisor identifies strengths and risks grounded in knowledge relationships. A higher strengths-to-risks ratio suggests better mitigation coverage in the current topology.
Healthcare Records Platform
0 strengths, 6 risks
Read-Heavy SaaS API
5 strengths, 2 risks
Migration Considerations
Migration Step 1
Healthcare Records Platform
Mutable clinical records with application-layer audit logging → Event-sourced clinical records with atomic audit event + outbox writes
Read-Heavy SaaS API
Single PostgreSQL, no cache, no pooling → PostgreSQL + PgBouncer + Redis cache
Both scenarios define a migration step at this stage. Healthcare Records Platform: triggered by 'HIPAA audit requirement exposed during external security rev'. Read-Heavy SaaS API: triggered by 'Connection pool exhaustion or p99 read latency > 200ms under'.
Migration Step 2
Healthcare Records Platform
Inline Kafka publish inside clinical transaction (dual-write) → Outbox pattern with CDC relay for FHIR event delivery
Read-Heavy SaaS API
PostgreSQL + PgBouncer + Redis cache → PostgreSQL + PgBouncer + Redis + streaming read replica
Both scenarios define a migration step at this stage. Healthcare Records Platform: triggered by 'FHIR events being published to Kafka but corresponding clini'. Read-Heavy SaaS API: triggered by 'Primary CPU > 70% during peak read hours'.
Migration Step 3
Healthcare Records Platform
All facilities sharing a single PostgreSQL cluster → Per-facility database with cross-facility patient index and record linkage
Read-Heavy SaaS API
No further migration step defined
Healthcare Records Platform has a defined migration; Read-Heavy SaaS API does not at this stage.
Advisor Notes
Strength: Redis caching absorbs repeated read requests at the edge, reducing database load and latency for high read-to-write ratio workloads by orders of magnitude
Redis caching absorbs repeated read requests at the edge, reducing database load and latency for high read-to-write ratio workloads by orders of magnitude. Key trade-off: Introduces eventual consistency: stale reads possible within TTL window. Operational note: Cache-aside (lazy population) is the dominant integration pattern. Evidence: Cache hit rates of 80–95% observed in production read-heavy APIs.
Risk (high): Replication Lag Cascade
Asynchronous replicas fall behind the primary under write load and serve reads from an older version of the data. Reads keep succeeding, so nothing errors; what breaks is one of three specific consistency guarantees (read-after-write, monotonic reads, or consistent prefix), each with a distinct user-visible anomaly.
Risk (high): Connection Pool Exhaustion
All database connections in the pool are in use; new requests queue and then time out, causing cascading latency and errors across all dependent services.
Shared Operational Requirements
Both scenarios require: Cache sizing and eviction policy configuration, PostgreSQL: scenario includes high_write_throughput or write_heavy workload, Redis: scenario has read_heavy workload with high cache miss risk.
Supporting Evidence · 16 items
Coverage Warnings
- ⚠Healthcare Records Platform: fewer than 2 architectural strengths identified. the risk/complexity dimensions are present but the strength analysis is thin. Consider enriching the relationship YAMLs referenced by this scenario to improve coverage.
Limitations
- ·Comparison grounded in YAML knowledge only. Not measured from any production system.
- ·Winner assessments are deterministic heuristics, not absolute recommendations. Context, team preferences, and workload specifics may change the conclusion.
- ·2 seed type(s) across both scenarios do not have execution previews. Risk confirmation for those types is unavailable.
- ·Neither scenario has a recorded consistency-guarantee claim. Guarantee comparison is uninformative for this pair, not silently empty.
Read-Heavy SaaS API is the recommended starting point over Healthcare Records Platform
Read-Heavy SaaS API leads on 4 weighted dimension(s): Complexity, Operational Risk, Operational Maturity. Weighted score: 6.5 vs 0.0 for Healthcare Records Platform.
Decision Intelligence
Architecture Decision Path
Structured reasoning for choosing between Healthcare Records Platform and Read-Heavy SaaS API. Every condition and trigger traces back to comparison dimensions, advisor insights, and topology evidence.
Read-Heavy SaaS API is the recommended starting point over Healthcare Records Platform
Read-Heavy SaaS API leads on 4 weighted dimension(s): Complexity, Operational Risk, Operational Maturity. Weighted score: 6.5 vs 0.0 for Healthcare Records Platform. The architectures share 4 component(s), reducing migration cost if you switch later. Read-Heavy SaaS API is the operationally simpler choice.
Where to Start
Start with Read-Heavy SaaS API
RightRead-Heavy SaaS API has lower operational complexity. Starting here reduces risk and cognitive load. Migrate to the more capable architecture only when you hit concrete scaling or feature limits.
Complexity: moderate complexity, 7 nodes, 6 edges, 2 risks, 2 simulation seeds
Migrate when:
- p99 database latency rising; connection wait queue growing; requests timing out with "too many connections" or pool queue full errors → Add PgBouncer connection pooler in transaction mode
- Database CPU > 80% sustained; read query p99 rising; cache miss rate stable but overall latency increasing → Add one or more streaming read replicas; implement lag-aware replica routing
- Redis hit rate < 60%; database read pressure rising despite cache presence; TTL expiry storms visible in Redis monitoring → Expand Redis memory allocation; segment cache by object lifecycle; implement staggered TTL jitter to prevent expiry storms
Decision Flow
Does your team have the operational maturity to run Healthcare Records Platform (advanced rating)?
If Yes
Your team can operate Healthcare Records Platform. Continue to Step 2 to refine based on risk tolerance and workload fit.
If No
Prefer the lower-maturity option: right scenario.
Is operational stability and minimising production risk your primary concern over feature richness or scalability ceiling?
If Yes
Prefer Read-Heavy SaaS API: it carries lower operational risk weight per the advisor's assessment.
If No
Proceed to Step 3 to evaluate based on scaling requirements.
Do you expect your load to reach: high sustained load with clear migration paths?
If Yes
Both scenarios have comparable scaling paths. Choose based on complexity preference.
If No
If you don't expect to hit these scaling signals soon, prefer the simpler architecture and re-evaluate when load patterns become clearer.
Does your team already operate an event streaming platform (e.g., Kafka, Kinesis, Pub/Sub) in production?
If Yes
Healthcare Records Platform builds on event stream infrastructure. Your existing platform reduces the adoption risk.
If No
If you don't have an event streaming platform, the other scenario avoids adding that infrastructure dependency. Evaluate whether the async decoupling benefit justifies the new ops burden.
Is operational simplicity (fewer moving parts, easier debugging, lower ops burden) more important than maximum architectural capability?
If Yes
Read-Heavy SaaS API is the simpler choice: Read-Heavy SaaS API is simpler: moderate operational complexity with 7 topology nodes vs 19 for Healthcare Records Platform.
If No
If capability and scalability ceiling matter more than simplicity, evaluate the higher-complexity scenario against your specific load model.
When to Choose Each Scenario
Healthcare Records Platform
LeftWhen your system requires decoupled async event processing
HighHealthcare Records Platform includes event stream infrastructure (e.g., Kafka/Kinesis), enabling async decoupling between producers and consumers.
Read-Heavy SaaS API
RightWhen operational simplicity is a top priority
HighRead-Heavy SaaS API has lower operational complexity: fewer moving parts, easier to reason about and debug.
When stability and predictability matter most
CriticalRead-Heavy SaaS API carries lower overall risk weight per the advisor's assessment.
When your team has limited operational maturity
CriticalRead-Heavy SaaS API is rated intermediate , accessible for teams without deep platform expertise.
When you want to minimise monitoring setup overhead
ModerateRead-Heavy SaaS API has a lower observability burden: fewer watched metrics and monitoring targets.
When your architecture benefits from: redis caching absorbs repeated read requests at the edge, reducing database load and latency for high read-to-write ratio workloads by orders of magnitude
ModerateRedis caching absorbs repeated read requests at the edge, reducing database load and latency for high read-to-write ratio workloads by orders of magnitude. Key trade-off: Introduces eventual consistency: stale reads possible within TTL window. Operational note: Cache-aside (lazy population) is the dominant integration pattern. Evidence: Cache hit rates of 80–95% observed in production read-heavy APIs.
When your architecture benefits from: a connection pool bounds the total database connections an application can open, preventing connection storms during traffic…
ModerateA connection pool bounds the total database connections an application can open, preventing connection storms during traffic spikes and protecting the database server from exceeding its connection limit. Key trade-off: Pooler becomes a new single point of failure if not replicated. Operational note: PgBouncer transaction-mode pooling is most effective for stateless APIs. Evidence: PgBouncer reduces PostgreSQL connections by 10–100x in typical deployments.
When to Avoid Each Scenario
Healthcare Records Platform
LeftWhen your team cannot mitigate: replication lag cascade
HighThis architecture is significantly exposed to Replication Lag Cascade. Asynchronous replicas fall behind the primary under write load and serve reads from an older version of the data. Reads keep succeeding, so nothing errors; what breaks is one of three specific consistency guarantees (read-after-write, monotonic reads, or consistent prefix), each with a distinct user-visible anomaly.
When your team cannot mitigate: lock contention
HighThis architecture is significantly exposed to Lock Contention. Concurrent writers to the same rows serialize behind each other's row locks, so latency is set not by the work a transaction does but by how long it waits for the writers ahead of it. On a hot row the queue depth, and therefore the tail latency, grows with concurrency while throughput flattens. Blocked writers hold connections open, so a single contended row can drain the connection pool as a secondary failure.
When your team is early-stage or solo
HighHealthcare Records Platform is rated 'advanced'. It requires experienced backend engineers or platform tooling to operate reliably at scale.
When you expect rapid growth within the next 12–18 months
ModerateThe advisor identifies 7 predicted bottlenecks for Healthcare Records Platform. Rapid growth will surface these limitations quickly.
Read-Heavy SaaS API
RightWhen your team cannot mitigate: connection pool exhaustion
HighThis architecture is significantly exposed to Connection Pool Exhaustion. All database connections in the pool are in use; new requests queue and then time out, causing cascading latency and errors across all dependent services.
When your team cannot mitigate: replication lag cascade
HighThis architecture is significantly exposed to Replication Lag Cascade. Asynchronous replicas fall behind the primary under write load and serve reads from an older version of the data. Reads keep succeeding, so nothing errors; what breaks is one of three specific consistency guarantees (read-after-write, monotonic reads, or consistent prefix), each with a distinct user-visible anomaly.
When you expect rapid growth within the next 12–18 months
ModerateThe advisor identifies 4 predicted bottlenecks for Read-Heavy SaaS API. Rapid growth will surface these limitations quickly.
Team Fit
Solo developer or small startup
RightRead-Heavy SaaS API is more accessible for small teams. Fewer operational moving parts reduces on-call burden.
- ↳Validate that the simpler architecture can handle your projected load before committing.
Small product team (2–6 engineers)
RightRead-Heavy SaaS API suits small teams that need to move fast without deep platform tooling investment.
- ↳Consider Healthcare Records Platform only if your workload pattern specifically requires it.
Experienced backend team
DependsAn experienced team can operate either architecture. Choose based on workload fit, not team capability.
- ↳Prioritise alignment with existing infrastructure and tooling.
- ↳Healthcare Records Platform may require additional runbook coverage and alerting investment.
Platform engineering team or SRE-equipped organisation
LeftA platform team can safely operate Healthcare Records Platform and will benefit from its more advanced scaling characteristics.
- ↳Ensure observability and alerting are configured before launch.
Migration Triggers
Migration Step 1
Both scenarios define a migration step at this stage. Healthcare Records Platform: triggered by 'HIPAA audit requirement exposed during external security rev'. Read-Heavy SaaS API: triggered by 'Connection pool exhaustion or p99 read latency > 200ms under'.
Migration Step 2
Both scenarios define a migration step at this stage. Healthcare Records Platform: triggered by 'FHIR events being published to Kafka but corresponding clini'. Read-Heavy SaaS API: triggered by 'Primary CPU > 70% during peak read hours'.
Migration Step 3
Healthcare Records Platform has a defined migration; Read-Heavy SaaS API does not at this stage.
Audit log table growing at > 500K rows/day; INSERT p99 on audit_log > 20ms; autovacuum unable to keep up with dead tuple accumulation from UPDATE operations on the audit log's index pages
Tier 1: Audit Log Write Throughput: Audit log receiving one row per record access creates I/O contention with clinical record writes on the same PostgreSQL primary. Recommended evolution: Partition the audit_log table by month using PostgreSQL declarative partitioning; child partitions allow VACUUM to operate on bounded table segments without scanning the entire history; index each partition independently to keep index size proportional to partition row count rather than total log size .
pg_locks showing RowExclusiveLock waits on clinical_records or encounter_notes during shift-change peak hours; write p99 > 100ms; occasional deadlock errors in application logs correlated with concurrent addenda writes to the same encounter
Tier 2: Concurrent Encounter Write Lock Contention: Multiple clinical staff members writing addenda to the same encounter simultaneously, or two processes updating encounter status concurrently. Recommended evolution: Implement optimistic locking with an encounter version column; reject concurrent writes with a conflict error and require the client to reload and retry; this eliminates lock waits by failing fast rather than waiting; ensure the application presents a clear conflict resolution UI: in a clinical context, silent overwrites of concurrent edits are a patient safety risk, not just a data integrity issue .
p99 database latency rising; connection wait queue growing; requests timing out with "too many connections" or pool queue full errors
Tier 1: Connection Exhaustion: Database connection pool saturated or max_connections exceeded. Recommended evolution: Add PgBouncer connection pooler in transaction mode.
Database CPU > 80% sustained; read query p99 rising; cache miss rate stable but overall latency increasing
Tier 2: Read Throughput Ceiling: Single PostgreSQL primary saturated with read traffic. Recommended evolution: Add one or more streaming read replicas; implement lag-aware replica routing.
Readiness Requirements
Cache sizing and eviction policy configuration
BothRedis or equivalent cache requires correct maxmemory configuration, eviction policy selection (allkeys-lru is common), and cold-start warming strategy after restarts.
PostgreSQL: scenario includes high_write_throughput or write_heavy workload
BothDeploy PgBouncer in transaction-mode pooling before relying on vertical scaling
Required maturity: mid_level
Redis: scenario has read_heavy workload with high cache miss risk
BothImplement cache stampede protection (probabilistic early expiry or locking) to prevent thundering herd on cold start
Required maturity: junior
Redis: scenario relies on Redis for data that cannot be re-derived
BothRedis is not a durable store: add persistence layer or treat Redis as expendable cache only
Required maturity: junior
Runbooks and alerting for high-severity risks
Both4 high-severity risks identified. Each requires a documented runbook, alerting threshold, and on-call response procedure before running in production.
Apache Kafka: scenario has team_maturity below senior
LeftKafka operational complexity requires dedicated expertise: consider MSK or Confluent Cloud to reduce ops burden
Required maturity: senior
Apache Kafka: scenario uses Kafka for event streaming or CDC
LeftSet min.insync.replicas=2 with acks=all; monitor consumer lag as primary health signal
Required maturity: senior
Event stream operations expertise
LeftThis architecture includes event stream infrastructure (Kafka, Kinesis, or similar). Operations requires consumer group management, partition assignment, dead-letter handling, and lag monitoring.
Required maturity: platform_engineering_team
Minimum team maturity: Platform Engineering Team
LeftThis scenario has expert operational complexity. It is recommended for Platform Engineering Team teams or higher.
Required maturity: platform_engineering_team
Minimum team maturity: Experienced Backend Team
RightThis scenario has moderate operational complexity. It is recommended for Experienced Backend Team teams or higher.
Required maturity: experienced_backend_team
Replica lag monitoring and lag-aware routing
RightRead replicas must be monitored for replication lag. The application router must include a max_lag_ms threshold; queries above that threshold must be redirected to the primary.
Generator Constraints
Healthcare Records Platform
LeftGenerator relevance documented but not yet production-ready.
For healthcare or compliance-heavy product briefs requiring full audit trails, the generator must output event sourcing + atomic audit log writes + outbox pattern as mandatory structural components, not optional enhancements. PostgreSQL RLS policy templates targeting patient-identifiable tables must be generated as non-optional. The generator must surface synchronous replication configuration (synchronous_commit setting and standby count) as an explicit output with a note about the per-write latency tradeoff.
Read-Heavy SaaS API
RightGenerator relevance documented but not yet production-ready.
This scenario is the most common initial architecture for read-heavy SaaS products. The generator should recommend this composition whenever the input brief specifies a read-heavy API workload with moderate consistency requirements. The technology and pattern selections here should be presented as a bundle, not as isolated independent recommendations.
Supporting Evidence
| Type | Reference | Explanation |
|---|---|---|
| Comparison | compare_healthcare_records_platform_vs_read_heavy_saas_api | Full comparison of Healthcare Records Platform vs Read-Heavy SaaS API: 6 dimensions, 4 shared components, 1 shared risks. |
| Advisor | advisor_healthcare_records_platform | Advisor for Healthcare Records Platform: 0 strengths, 6 risks, maturity: advanced. |
| Advisor | advisor_read_heavy_saas_api | Advisor for Read-Heavy SaaS API: 5 strengths, 2 risks, maturity: intermediate. |
| Scenario | healthcare_records_platform | Scenario 'Healthcare Records Platform': 4 scaling thresholds, 3 migration paths, complexity: expert. |
| Scenario | read_heavy_saas_api | Scenario 'Read-Heavy SaaS API': 4 scaling thresholds, 2 migration paths, complexity: moderate. |
| Risk Path | prop_architecture_pattern_read_replica_risk_replication_lag_cascade | Read Replica → Replication Lag Cascade |
| Risk Path | prop_workload_profile_write_heavy_transactional_risk_lock_contention | Write-Heavy Transactional → Lock Contention |
| Risk Path | prop_technology_profile_redis_risk_connection_exhaustion | Redis → Connection Pool Exhaustion |
| Risk Path | prop_architecture_pattern_read_replica_risk_replication_lag_cascade | Read Replica → Replication Lag Cascade |
| Risk Path | prop_architecture_pattern_read_replica_risk_replication_lag_cascade | Referenced by the operational risk comparison dimension. |
| Risk Path | prop_workload_profile_write_heavy_transactional_risk_lock_contention | Referenced by the operational risk comparison dimension. |
Limitations
- ·Decision guidance is grounded in YAML knowledge only. Not measured from any production system.
- ·Recommendations are deterministic heuristics based on structured knowledge. Your specific workload, team profile, and business context may lead to different conclusions.
- ·Generator constraints are preliminary. No scenario should be treated as production generation-ready at this stage.
Comparison complete
Profile, topology, simulation, advisor, comparison, and decision path are ready. Your architecture decision is grounded in structured knowledge and deterministic reasoning.