cqrs-es

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even

Feature Request

Description

We currently need to have consistent reads active to manage the case when we write a new version of the read model and read it in the same lambda execution. For instance, when we're processing the event stream and updating the entities, then read models are updated. We need to make sure that the second time we read them we get the same object we stored in th

I hate manual tagging because, as everything tasked to a human being, the human factor brings inherent error.

Since we're all ✨ software engineers here ✨ we can automate the tagging process when merging on main -- maybe after the tests have passed?

NOTE: for each feature, a minor release should be used, and fix or minor branch, a patch release should be used instead.

Or maybe a whale with little squares on top ... ! Or perhaps an apple!