Stop Punching Yourself in the Face
summary
A series of concrete failures and fixes: storing raw text in RavenDB cost per GB vs S3 teaches to check technical fit; choosing Agata that stopped being maintained becomes Agata abandoned — use Mediator; adding EventStore for audit trails creates a single-expert bottleneck (EventStore knowledge silo) until the team builds shared POCs; Entity Framework problems trace to DBContext startup, N+1 queries, missing indexes and wrong projections; prefer a simple monolith and plan refactors when replacing tech.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:43What we do
- 1:01The magpie
- 1:37The software developer
- 2:18Is this surprising?
- 3:18Our education
- 4:12We look for guidance...
- 5:10until we run into a wall!
- 5:53The RavenDB story
- 9:42The Agatha story
- 15:06The EventStore story
- 18:45The Entity Framework story
- 23:09The "big old project" story
- 26:40The Microservices story
- 32:16Summary
related talks
50mStop Punching Yourself in the Face
40mStop punching yourself in the face!
30mHow Event Driven Architectures Go Wrong & How to Fix Them
49mAvoiding mistakes with events, one at a time
56mBuilding That Glorious Monolith. And Carving It Too
48mEvent Sourcing - what could possibly go wrong?
48m9 Fallacies of Event driven Architectures
41mArchitecture aspects - evolutionary architecture development