Thanks for the post. I’ve asked multiple times multiple questions in the forums that never got a single answer. My major concern has always been to “keep history”.
I never started with Strapi because I felt there was not enough community.
If it supported CQRS+ES then migrations and so on would be 100% guaranteed and future compatible: You just export the book of events in version n and re-import them in version n+1.
More important: If it supported CQRS+ES, you would not lock-in Strapi: You can use strapi when bootstraping your startup and if at any point you get stuck by scalability, you can re-use the events in any newer system (even old strapi + new custom systems could co-exist going to the same event store).
I even wonder if the Strapi architects are on the “Event Sourcing” bleeding edge. I feel them stuck to the old-fashioned CRUD ideas of the last century.
@fahidmohammad Did you choose any other general-purpose platform? Or you going to custom?
PD: In regards to what @DMehaffy says I feel there’s a misunderstanding about the conception of “open source justifies the public product is below par and if you pay you’ll go the right way”. People from mautic are on the same error than Strapi. Mautic’s open source versions do not scale and have lots of breaking errors. And if you want it to seamlessly work, they say “pay”.
But this is not a justification. MariaDb, docker, gimp, the linux kernel, apache, nginx, php, kubernetes, jenkins, flutter, or elasticsearch are just a few that being Open Source are on-par or even above par for the 100% free version.