You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
When implementing a microservices architecture, we are unclear how to define the database schema. We are considering two options:
Single schema for the entire application: All services would communicate with a single database, which would act as another service, similar to the Blackboard pattern.
Pure microservices model: Each microservice would have its own independent database.
Due to this issue, the database schema is currently on hold. We need to define the architecture we will use for data persistence before we can implement the necessary schema(s).
In any case, we have decided to use a common Miro diagram to define the data model, which we will need regardless of the architecture chosen.
Define the data base schema of the application.
The text was updated successfully, but these errors were encountered: