Event Sourcing is not a silver bullet and should be evaluated at the module level rather than as a system-wide decision. Simple CRUD systems — like CMS or configuration services — are poor fits, though seemingly simple systems can evolve into complex workflows. Three socio-technical factors matter beyond technical fit: a team that works well with its current approach shouldn't change for change's sake; reluctant teams may need gradual evangelism through small proofs of concept; and over-enthusiastic teams risk introducing complexity before they understand the domain. The recommended approach is 'Start Small - Grow Big' — begin with a low-risk, audit-friendly feature to learn before committing broadly.

9m read timeFrom event-driven.io
Post cover image
Table of contents
Event Sourcing is not a silver bullet.Technical considerations are not the only ones we should evaluate.That’s the second category of socio-technical issues: reluctance.That’s how we came to the third socio-technical category: over-enthusiasm
2 Impressions