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

Deployment outputs (baseURL, graphQL endpoint, etc.) are shown once the application is deployed to your cloud provider of choice, but once you close the terminal window, the only way to see these outputs is by rerunning the deployment.

Possible Solution

Create a separate CLI command to see the current deployment status. For instance:

$ boos

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.