Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Event Sourcing was popularized by LMAX as a means to provide speed, performance scalability, transparent persistence and transparent live mirroring. Before being rebranded as Event Sourcing, this type of architectural pattern was known as System Prevalence but yet I was never familiar with this pattern before the LMAX team went public.

Has this pattern proved itself in numerous production systems and therefore even conservative individuals should feel empowered to embrace this pattern or is event sourcing / system prevalence an exotic pattern that is best left for the fearless?

share|improve this question

closed as primarily opinion-based by MichaelT, Bart van Ingen Schenau, Michael Kohne, GlenH7, amon Mar 9 at 10:11

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

2  
Event Sourcing has been around for a long time and I believe that LMAX's former CTO (and creator of the Disruptor) has cited several academic and industry papers that he based a good chunk of this on. I'll ping him and get him to chime in here. –  Martijn Verburg Jun 7 '12 at 7:39

1 Answer 1

up vote 7 down vote accepted

The concepts behind Event Sourcing have been around a long time, and often with other names. Tandem computers were built on this idea as was IBMs IMS TM. IMS TM was developed for the Apollo space program in the 60s and Tandem appeared in the 70s.

Many modern high-performance systems for the financial domain are built on such patterns. Almost all are custom builds. Unfortunately no one to my knowledge has offered a product that supports Event Sourcing and CQRS to a suitable standard for production systems. It is something I've often considered doing having built many such systems over the years. Just never had the right opportunity.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.