Three Rewrites, One Startup - An Architect's Journey
summary
A construction-integration product undergoes three major rewrites: from a scheduled ETL and stored-procedure monolith with on-prem connector agents to a Windows-service distributed monolith using RabbitMQ and generated SQL mappings, then to a message-driven, record-by-record platform backed by Azure Cosmos DB and Azure Service Bus. Early system has no automated tests, manual hour-long deployments, and frequent duplicate-data bugs; later phases add strong testing, turnkey CI/CD, per-record workflows, and much lower latency.
AI-written summary · about
chapters (24)
- 0:00Start
- 0:55The Company
- 2:06The Person
- 7:24Rules for playing around in prod
- 7:38PARANOIA
- 11:27Requirements
- 18:04The Rewrites
- 19:25Data Process App
- 20:21Uploading
- 21:01Syncing
- 21:29Downloading
- 21:44Retrospective
- 22:15Problems
- 25:27Things to fix
- 26:08Honey do list
- 26:40Goals
- 27:33Connector Service
- 27:49Cloud Service
- 38:23Advantages
- 39:10Real-time
- 39:46With the bitter comes the sweet
- 45:12High-level workflow
- 47:43Lots of early wins
- 50:02Thank you!
related talks
51mTo Re-write Or Not To Re-write
23mOn the road from Monolith to Micro
24mArchitecting the Unconventional: A Case Study in Software Design
40mSmoothing the continuous delivery path- a tale of two architectures
45mUsing modern .NET technologies to decompose a monolith into micro-services
43mDesigning software in the cloud
01h 35mRedesigning Legacy Systems - Keys to Success / Lessons Learned
40mHow to sell a big refactor or rewrite to the business?