Aggregate root & Repository dilemma
I am in a big dilemma here.
Is this an example of a composition or aggregation? [duplicate]
This question already has answers here: Aggregation vs Composition (9 answers) Closed 7 years ago. Composition and aggregation both are confusion to me. Does my code sample below indicate composition or aggregation? class A { public static function getData($id) { //something } public static function checkUrl($url) { // something } class B { public function […]
DDD – Aggregate Roots – Dealing with Efficiency and Concurrency
First off, I’ll admit that I’m a newbie to DDD and need to read the “blue book”.
pre aggregating documents mongodb
In our current setup, most of our database calls are updates where we increment a key by 1.
pre aggregating documents mongodb
In our current setup, most of our database calls are updates where we increment a key by 1.
pre aggregating documents mongodb
In our current setup, most of our database calls are updates where we increment a key by 1.
Aggregate design for a fuel tank with deliveries and fill level readings
So I’ve got a rather simple, mostly crud application I want to use DDD with, to learn/practice it. I wonder about aggregate design regarding a fuel tank entity. Each tank stores fill level readings (date, fill level), usually one each year, and gets several deliveries of fuel per year (date, amount, cost).
Looking at invariants, the two collections are independent from each other, and I can only see one business rule for the fill level readings: there must only be one reading for any given date.
Regarding usage patterns, the two collections are edited independently as well, because a delivery rarely happens on the same day that readings are taken. When reading a tank to display it, however, the most recent values of both collections are also needed.
Aggregate design for a fuel tank with deliveries and fill level readings
So I’ve got a rather simple, mostly crud application I want to use DDD with, to learn/practice it. I wonder about aggregate design regarding a fuel tank entity. Each tank stores fill level readings (date, fill level), usually one each year, and gets several deliveries of fuel per year (date, amount, cost).
Looking at invariants, the two collections are independent from each other, and I can only see one business rule for the fill level readings: there must only be one reading for any given date.
Regarding usage patterns, the two collections are edited independently as well, because a delivery rarely happens on the same day that readings are taken. When reading a tank to display it, however, the most recent values of both collections are also needed.
Aggregate Boundary repository/service design
I am trying to apply DDD to the design of a Release Management system.
Aggregate Boundary repository/service design
I am trying to apply DDD to the design of a Release Management system.