Two-Sided Marketplace Platform
Not ReadyTwo-Sided Marketplace Platform requires expert operational expertise at 'platform engineering team' level. Current readiness estimate is 20%, critical gaps must be resolved before adoption. Consider starting with a simpler scenario and evolving toward this one.
Readiness Score
20%
Blocking Prerequisites
4
Complexity
Expert
Confidence
StrongPrerequisite Checklist
team
Team at 'platform engineering team' maturity level
This scenario is rated 'platform engineering team' complexity.
Gap signal: Team frequently reaches for external help during incidents or struggles to debug multi-system issues independently.
process
Failure mode awareness and runbooks
The team must understand the 5 documented failure modes for this scenario: hot_partition, cascading_failure, lock_contention, thundering_herd. Each should have a documented detection procedure and runbook.
Gap signal: The team has no documented runbooks for the scenario's failure modes or cannot name them without reference material.
monitoring
Production-grade observability stack
The scenario requires real-time metrics, structured logging, and distributed tracing on all critical components. Alerting must be configured before going live.
Gap signal: No dashboards exist for the critical path metrics in the scenario.
infrastructure
Minimum team maturity: Platform Engineering Team
This scenario has expert operational complexity. It is recommended for Platform Engineering Team teams or higher.
Gap signal: The requirement 'Minimum team maturity: Platform Engineering Team' is not yet in place.
infrastructure
Runbooks and alerting for high-severity risks
5 high-severity risks identified. Each requires a documented runbook, alerting threshold, and on-call response procedure before running in production.
Gap signal: The requirement 'Runbooks and alerting for high-severity risks' is not yet in place.
infrastructure
Event stream operations expertise
This architecture includes event stream infrastructure (Kafka, Kinesis, or similar). Operations requires consumer group management, partition assignment, dead-letter handling, and lag monitoring.
Gap signal: The requirement 'Event stream operations expertise' is not yet in place.
infrastructure
Mitigation for 2 high-risk topology node(s)
Nodes with high or critical risk exposure: Marketplace Mixed, Redis. Each requires documented mitigation before production deployment.
Gap signal: No mitigation strategy is documented for the high-risk nodes in the topology.
Infrastructure Requirements
Elasticsearch
high burdenDistributed full-text search and analytics engine built on Apache Lucene, designed for near-real-time indexing, complex search queries, and log analyt
Managed: Elastic Cloud (Elastic.co), Amazon OpenSearch Service, Elastic Cloud on Kubernetes (ECK)
Apache Kafka
high burdenDistributed event streaming platform designed for high-throughput, fault-tolerant, ordered, and durable log-based messaging between producers and cons
Managed: Amazon MSK (Managed Streaming for Kafka), Confluent Cloud, Azure Event Hubs (Kafka-compatible), Redpanda Cloud
PostgreSQL
medium burdenACID-compliant relational database with strong consistency, JSONB support, full-text search, and mature replication.
Managed: Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, Google Cloud SQL for PostgreSQL, Azure Database for PostgreSQL, Supabase, Neon
RabbitMQ
medium burdenAMQP-based message broker with flexible routing (exchanges, queues, bindings), acknowledgment-based delivery, and per-message TTL and dead-letter queu
Managed: CloudAMQP, Amazon MQ for RabbitMQ, Azure Service Bus (AMQP-compatible)
Redis
low burdenIn-memory key-value store with optional persistence, supporting strings, hashes, lists, sets, sorted sets, and pub/sub.
Managed: Amazon ElastiCache for Redis, Google Cloud Memorystore, Azure Cache for Redis, Redis Cloud, Upstash
Observability Requirements
Monitor read hotspot signals
Seed 'Read Hotspot Saturation' identifies 3 metrics relevant to hot_partition. Execution preview confirms this risk manifests under modelled load.
Seed 'Read Hotspot Saturation' identifies 3 metrics relevant to hot_partition. Execution preview confirms this risk manifests under modelled load.
Monitor generic risk probe signals
Seed 'Thundering Herd (Cache Stampede) Risk Probe' identifies 2 metrics relevant to thundering_herd.
Seed 'Thundering Herd (Cache Stampede) Risk Probe' identifies 2 metrics relevant to thundering_herd.
Track Hot Partition exposure
Hot Partition has high exposure and affects 1 component. Affects 1 node. (Marketplace Mixed)
Hot Partition has high exposure and affects 1 component. Affects 1 node. (Marketplace Mixed)
Track Cascading Failure exposure
Cascading Failure has high exposure and affects 0 components. Affects 0 nodes
Cascading Failure has high exposure and affects 0 components. Affects 0 nodes
Track Lock Contention exposure
Lock Contention has high exposure and affects 0 components. Affects 0 nodes
Lock Contention has high exposure and affects 0 components. Affects 0 nodes
Redis cache miss spike visible in monitoring; PostgreSQL query rate spiking for listing reads despite stable write volum
This signal indicates the architecture is approaching 'Tier 1: Viral Listing Thundering Herd'. Likely bottleneck: Cache TTL expiry on hot listings during peak traffic: all concurrent requests bypass cache simultaneously.
Tier 1: Viral Listing Thundering Herd
Saga compensation events appearing in order event log; checkout p99 > 2s; pg_locks showing contended rows on inventory_r
This signal indicates the architecture is approaching 'Tier 2: Checkout Saga Contention'. Likely bottleneck: Concurrent checkout transactions competing for the same inventory rows; saga timeout thresholds too aggressive.
Tier 2: Checkout Saga Contention
RabbitMQ queue depth > 100k messages; notification delivery latency > 5 minutes; downstream notification provider (SendG
This signal indicates the architecture is approaching 'Tier 3: Notification Queue Backlog'. Likely bottleneck: Notification consumer throughput insufficient for event fanout rate; or downstream provider rate limiting.
Tier 3: Notification Queue Backlog
Readiness Action Plan
Satisfy: Team at 'platform engineering team' maturity level
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Two-Sided Marketplace Platform
Satisfy: Failure mode awareness and runbooks
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Two-Sided Marketplace Platform
Satisfy: Production-grade observability stack
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Two-Sided Marketplace Platform
Satisfy: Mitigation for 2 high-risk topology node(s)
Effort: 1–4 weeks depending on current state · Unblocks: Adoption of Two-Sided Marketplace Platform
Instrument all critical path components with metrics and alerting
Effort: 1–2 weeks · Unblocks: Safe production adoption and incident response
Validate adoption in a staging environment before production
Effort: 2–4 weeks for thorough staging validation · Unblocks: Production confidence and rollback preparedness
Mitigate risk: Hot Partition
Effort: 1–3 weeks · Unblocks: Reduces 'Hot Partition' from blocking adoption
Mitigate risk: Cascading Failure
Effort: 1–3 weeks · Unblocks: Reduces 'Cascading Failure' from blocking adoption
Readiness assessment is derived from structured scenario and topology knowledge. It provides an evidence-grounded baseline, not a substitute for an actual team capability review or infrastructure audit. Validate each item against your specific environment.