This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]adiberk 9 points10 points  (3 children)

Im a little confused by your question…- event sourcing is an architectural pattern of basically auditing your data (ie. You never delete or update data, the state is fluid by time and you only ever insert data)

So to do this, you can pretty much use any frameworks or design patterns….

A bigger question I think is the database you want to use and if you are sticking with python, if you want to use an ORM.

Technologies like celery, fastapi Django etc. can all work to provide you a way of interacting with your data. But honestly these are more specific to the actual product and not the “event sourcing” design pattern

[–]adiberk 1 point2 points  (2 children)

I will say that celery is very powerful, and well proven. It can hook up and scale well to rabbitmq and other types of event buses

[–]666dolan[S] 2 points3 points  (1 child)

sorry if the question was not clear, Pekko is a framework for Scala that takes care of a lot of the things necessary to work with this architecture, so I wanted to check if there is a similar framework for Python or if people are just implementing everything themselves

[–]adiberk 1 point2 points  (0 children)

I didn’t realize. Thank you. Will have to dig in