Support chat for http://getprooph.org/ - official announcement: https://www.sasaprolic.com/2018/08/the-future-of-prooph-components.html
1 reply
@prolic Prooph hereby announces that the development of prooph/service-bus and prooph/event-sourcing will be dropped. This also includes all snapshot-store implementations as well as message producers.
In fact, we recommend not using any framework or library as part of your domain model, and building the few lines of code needed to implement a left fold yourself - partly to ensure understanding and partly to keep your domain model dependency-free. The event-sourcing component was always meant to be a blueprint for a homegrown implementation but most people installed and used it as is, thus the prooph core team was complicit in advertising bad practices.
Since I came across Event Sourcing, I have spent hours learning about ES, DDD and BDD. I have Gregory Young say it a couple of times where he mentions that we shouldn't use a framework for Event Sourcing and here I think I have found a library that could save me the time of reinventing the wheel again only to come across this blog post.
My question is: should we use Prooph's Component in our projects in 2022 and beyond or not?
If I understand, I can choose certain components to use in my projects.
If so, then please let me know which components is still supported and those that are deprecated
https://github.com/prooph/event-store/tree/7.x#version-guidance
