Don’t Get Blamed for Your Choices
summary
Team stores raw text files in Raven DB used as blob storage, driving up cost and ops overhead instead of cheap Azure Blob storage; choosing an unmaintained framework like akkada/akka risked a single vanished maintainer; an EventStore wrapper centralizes work on one developer and the rest never touch events; Entity Framework perf issues trace to n+1 queries, missing indexes and cold DbContext, not magic; full microservices + MongoDB + Kubernetes on a simple greenfield app creates big delays.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:19The Raven DB Story
- 5:57RAVENDB
- 7:25Technical fit
- 8:49The Agatha Story
- 11:13Check for warning signs
- 14:36Team skills
- 16:04The Entity Framework Story
- 19:12Take away the magic
- 20:04The Big Old Project Story
- 22:19Trim your stack
- 27:17Evolving architecture
related talks
50mStop Punching Yourself in the Face
01h 00mHigh Optionality Programming: Architectural Choices That Mitigate Technical Debt
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
36mApps, stacks & frameworks: Avoiding "Shiny Object" Syndrome
19mMistakes Were Made
22mMicroservices Highway to hell
01h 02mOpening Keynote: FIXME
48mHow (not) to build a startup?