Startups Don't Die from Choosing the Wrong Framework
summary
Engineers recount building a startup product with complete freedom to choose technology and then adopting microservices, event-driven architecture, and modern cloud tooling from day one. They analyze trade-offs and slowdowns caused by those choices, explain when infrastructure decisions helped or hindered the business, and share concrete lessons on what they would change or keep to prevent architecture from distracting from product delivery.
AI-written summary · about
chapters (16)
- 0:00Technical debt
- 1:26Startup vs corporate
- 3:53Early tech challenges
- 9:36Customization trap
- 12:04Tech stack debates
- 15:14Enterprise tech transfer
- 18:25Overengineering risks
- 21:56Tech ego pitfalls
- 24:00Team governance
- 27:32Good enough
- 29:15Automation & deployments
- 31:24Monitoring & observability
- 32:26Teamwork matters
- 33:47Tech meets business
- 34:28Startup failure causes
- 35:30Q&A
related talks
52mMicroservices as the Worst Architectural Choice for a Startup
59mChoosing the Right Architecture Style Debate
54mSoftware and architecture quality in a startup
25mThinking Architecturally
48mCrashmanship, Architecture from Start-up to Scale-up
23mPlatform Engineering for Architects - Crafting Platforms as a Product
39mMinimal Viable Architecture
43mStartup Architecture – How much “it depends”?