8
votes
Accepted
When would you consider sharing a database to be fine? What are your rules?
Your "components" should probably be part of the same "service", even if they are run as different executables. If this is the case it should be fine if both access the same ...
- 4,387
7
votes
Accepted
How to structure repositories for a small number of entities?
In DDD, the general approach is to have one repository per aggregate.
An aggregate is a collection of closely related concepts that together form a consistency boundary.
For example an Order aggregate ...
- 4,709
3
votes
Accepted
How does a Bounded Context from DDD help scaling microservices?
Bounded Contexts as a strategic pattern have several benefits:
They are linguistic boundaries. A concept may have a different meaning to different parts of the business. By acknowledging this and ...
- 4,709
2
votes
When would you consider sharing a database to be fine? What are your rules?
Working through your options:
The background worker subscribes to "credit" domain events emitted by the REST API and stores the consumer' credit in its own database.
My primary concern for ...
- 2,582
1
vote
When would you consider sharing a database to be fine? What are your rules?
The main problems with sharing a database is that if the database ever requires refactoring, it is much more difficult to perform refactoring on a database than it is to perform refactoring on an API.
...
- 660
Only top scored, non community-wiki answers of a minimum length are eligible