Timeline for Some thoughts on the Repository pattern
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2021 at 6:21 | vote | accept | qUneT | ||
| Jun 9, 2021 at 15:20 | comment | added | T. Sar | Worth to note - Repository Pattern usually uses other methods - read: other patterns - to do a lot of the work. You rarely can use a single pattern alone in a vacuum. Most often than not, they are mashed up and combined with other patterns to get a bigger job done. So, it's fairly usual that you see a lot of people implementing Reps on very different manners. | |
| Jun 8, 2021 at 8:28 | answer | added | Flater | timeline score: 1 | |
| Jun 8, 2021 at 2:59 | answer | added | VoiceOfUnreason | timeline score: 1 | |
| Jun 7, 2021 at 17:05 | answer | added | Ewan | timeline score: 2 | |
| Jun 7, 2021 at 16:10 | comment | added | Doc Brown | See also: How does “Composition Root” DI apply to Domain Driven Design?. In short, the "Composition Root" is the place where a concrete repository gets instantiated. | |
| Jun 7, 2021 at 16:06 | comment | added | Doc Brown | Related: Which layer do DDD Repositories belong to? | |
| Jun 7, 2021 at 16:05 | review | Close votes | |||
| Jun 13, 2021 at 3:06 | |||||
| Jun 7, 2021 at 16:04 | comment | added | Sumanth Kumar Mora | Aggregates are the basic element of transfer of data storage - you request to load or save whole aggregates. Transactions should not cross aggregate boundaries. You can refer to more documentation here martinfowler.com/bliki/DDD_Aggregate.html | |
| Jun 7, 2021 at 16:00 | comment | added | Sumanth Kumar Mora | In general, aggregate root is the only reference that is passed around. In DDD other entities without aggregate root aren't referable in business. it also means whenever you load/retrieve an information from persistence layer, you should have a way to map it to the aggregate root. | |
| Jun 7, 2021 at 15:48 | history | asked | qUneT | CC BY-SA 4.0 |