I remember a long time ago there was a fashion for "prevalence layers" instead of persistence layers. The idea being you persist your event log, but your app is

I remember a long time ago there was a fashion for "prevalence layers" instead of persistence layers. The idea being you persist your event log, but your app is the materialisation of all those events replayed. That way you get stop-the-world persistence but you're only ever dealing with your domain model (or the event sourced version of it, at least). Obviously you then run into issues around the size of the working set, and querying use cases. The approach in the article seems like an attempt to have your cake and eat it, and so my gut reaction is that it won't work, but then I never really had an issue with ORMs in the first place - Hibernate was great and I don't think I've seen an approach in 15+ years that convinces me we've moved forwards.