software engineering: where does business logic go that involves multiple aggregates?
Published 1 year ago • 1 view plays • Length 2:13Download video MP4
Download video MP3
Similar videos
-
4:28
software engineering: cqrs, where exactly is business logic that coordinates between aggregates?
-
2:32
software engineering: where should business logic go in a layered architecture? (2 solutions!!)
-
3:17
software engineering: ddd with orm where should the business logic go? (3 solutions!!)
-
1:32
software engineering: syncing business logic across multiple levels
-
2:49
software engineering: how to best organize multiple webprojects that use similar business logic?
-
2:43
software engineering: reusing business logic layer in multiple applications
-
2:10
software engineering: maintain server business logic for multiple version of offline client
-
2:08
software engineering: data vs business logic (2 solutions!!)
-
52:10
the otbase user interface
-
8:29
𝐖𝐡𝐚𝐭 𝐢𝐬 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐜𝐞 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐏𝐫𝐨𝐟𝐢𝐛𝐮𝐬 𝐚𝐧𝐝 𝐏𝐫𝐨𝐟𝐢𝐧𝐞𝐭? 𝟐𝟎𝟐𝟒
-
50:23
connell watkins - - onion architecture with ddd and cqrs
-
2:54
software engineering: reuse business logic between web and api (2 solutions!!)
-
2:15
software engineering: where should i place business logic validations? (2 solutions!!)
-
3:07
software engineering: ddd and mediatr - where the validation and business logic go
-
3:20
how can i write complex validation and business logic that can be reused in both direct data...
-
3:39
software engineering: business logic outside shared orm models (2 solutions!!)
-
3:10
software engineering: keeping business logic separate from data access (3 solutions!!)
-
1:50
software engineering: seperating business logic and layout in a highly interlocked project
-
2:07
software engineering: entity framework 5, separating business logic from model - repository?
-
1:40
software engineering: how to properly wrap my data layer to communicate with business logic?
-
3:10
how to handle child objects that need db interaction for their business logic?
-
1:51
software engineering: encapsulating business logic that goes beyond validations in mvc