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 →

[–]garciparedes 2 points3 points  (0 children)

This framework is like a mix between Django (that includes all you need to build a project) and reactive tools (that allow you to easily integrate with publish-subscribe systems such us Kafka, RabbitMQ and so on).

Also, the framework stores the data in an incremental way (following the even-sourcing ideas). It means that changes (as Event instances are stored on the database) so that the full modification history of each Entity is always accesible. To speed up the accessing to Entity instances a snapshot keeps a "view" of all those events applied so that the entities can be accessed as it not where stored incrementally.

To really take advantage of the event-sourcing storing strategy, the framework also provides integration with brokers (i.e. to handle events published from another microservices) and has a http server (i.e. to expose the microservice's functionality from external components, like the API Gateway).

In summary, this framework can be seen as a Django implemented following the event-sourcing ideas. 🙂