Autostore MS
Robotic Warehouse Automation
Warehouse automation platform controlling robotic cart fleets — DDD core, RabbitMQ messaging fabric, Kafka log analytics, Azure data pipelines and BI reporting.
The problem
Keep a fleet of warehouse robots operating through failure: decouple services so high-load robotic operations degrade gracefully, and turn automation logs into SLA and fault intelligence.
System topology
Hover or tap any component. Amber packets carry control and approvals; cyan packets carry data.
Component inspector
Select any component in the topology to see the technology behind it, why it was chosen, and the trade-off accepted with it.
Decision log
The choices that shaped the system, and what each one cost.
Two messaging systems, two jobs
RabbitMQ carries commands and domain events where routing flexibility matters; Kafka carries high-volume log streams where replay and ordering matter. Choosing one for both would compromise both.
DDD where the domain earns it
Robot task allocation, inventory and routing rules are the business — bounded contexts kept a growing team from turning them into mud. CRUD corners stayed plain CRUD.
Resilience through decoupling
Exchange topologies ensure a failing consumer (logging, alerting, BI) never back-pressures robot operations. The warehouse keeps moving while dashboards recover.