Three Rewrites, One Startup - An Architect’s Journey
summary
Three rewrites over four years take a one-off integration into a product then SaaS then a platform, moving from ASP.NET Web Forms + SQL Server stored‑procedure syncs to RabbitMQ/Twilio real‑time glue, then to Azure Service Bus + Cosmos DB and record‑based processing. Built self‑updating connector Windows services (TopShelf), a cloud scheduler, and a code‑generation layer that emits SQL to eliminate many duplicates; result: faster deployments, real‑time workflows, and hundreds of unit and integration tests that let teams sleep on Fridays despite lingering migration pain.
AI-written summary · about
chapters (38)
- 0:00Intro
- 1:07What is Rivet
- 2:29Spencers humble beginnings
- 7:34Rules for playing around
- 10:45Getting stuff done
- 13:18Message queues
- 17:30Fragile deployments
- 20:02Getting stuff done at a cost
- 23:47Integration
- 25:14Dragons
- 27:56Fixing Problems
- 30:05Reuse the Stuff
- 31:32Cloud Service
- 33:35DevOps Jenkins
- 36:05Data Cache
- 38:02Stored Procedures
- 42:19What Fits
- 45:15Sequel
- 48:12What Didnt
- 48:35Scaling
- 48:56Developer Tools
- 49:51Is In Better Than Being Consistent
- 50:25Compliment Their Strengths
- 50:49Pair Programming
- 51:10Embrace Imperfect Code
- 51:38Launch Too Late
- 51:57Third Rewrite
- 53:10Cosmos DB
- 53:40Decouple
- 54:06Record Based Processing
- 54:58Cloud
- 56:38Business vs Technology
- 57:14Current Architecture
- 57:27Legacy Matters
- 57:46Monoliths
- 58:25Early Wins
- 59:00Whats Next
- 59:19You Cant Do It Forever
related talks
51mCompleting the Rewrite from Hell: Five Years of Technical Debt and How We Escaped
27mBig Rewrite Strikes Again
42mSo You Want To Rewrite That...
33mTaylor’s Guide to Big Rewrites
15mTransitioning 69,000 engineers to one cloud system
27mMicro-transformation
22mMicroservices Highway to hell
54mDesigning for change with Vertical Slice Architecture