Re: DDD Introduction Talk http://channel9.msdn.com/Events/TechEd/Europe/2014/DEV-B411 https://msdn.microsoft.com/en-us/magazine/dn342868.aspx I think this will give you the desired
Re: DDD Introduction Talk There area loads of them that you can watch for free on www.skiilsmatter.com . On Tue, Feb 24, 2015 at 1:24 AM, Alex Paransky apara@...
Re: DDD Introduction Talk http://www.infoq.com/presentations/strategic-design-evans 2015-02-23 7:04 GMT-03:00 christian.helmbold@... [domaindrivendesign] < ... -- *Att,* *Veranildo
Fetching Sponsored Content...
Re: DDD Introduction Talk There are quite a few overview videos on YouTube. Perhaps starting with those would work? On Feb 23, 2015 4:06 PM, "christian.helmbold@...
DDD Introduction Talk Hi, I want to introduce my team to domain driven design and thought it would be a good idea to let some real expert speak to them (via Youtube or the like). Do
New DDD group in Atlanta (ATL) Hello Everyone, I am announcing a new group for those who live in Atlanta, GA (USA). Find details here... http://www.meetup.com/DDD-CQRS-ATL/ Feel free to
Re: Same aggregate in 2 bounded contexts @Greg I always thought that a BC maps 1-to-1 with a service! I won't hide the fact that I've only built monolithic applications with no real notion of
Re: Same aggregate in 2 bounded contexts I didn't know you had two different databases. In that case, like I told you earlier, use events to notify BCs about changes. That way you can pass in the
Re: Same aggregate in 2 bounded contexts There is a difference between a bounded context and a service. Have you looked into raising events about suppliers? On Sat, Jan 3, 2015 at 3:56 AM,
Re: Same aggregate in 2 bounded contexts I think I should have mentioned that each BC will have its own database and it will run on a different server and maybe managed by a different team. So when
Re: Same aggregate in 2 bounded contexts I think you're a little confused with the concepts of DDD. Your persistence layer will guarantee that you have your entities "sync" because after all your
Re: Same aggregate in 2 bounded contexts Hi Why would you want to keep the entities in sync? e.g. Do you really need the information about whether a supplier is disable in both BCs? if the answer is
Re: Same aggregate in 2 bounded contexts Thanks Jose for your reply. so we agree that I can have the same entity Supplier in multiple BCs. My next question is how can I keep those entities in sync?
Re: Same aggregate in 2 bounded contexts I believe Suppliers doesn't have to be a BC. If there's not business logic and just CRUD operations, than you can just use a plain CRUD repository to deal with
Same aggregate in 2 bounded contexts Let's model this scenario: We are trying to connect to different "Suppliers" via FTP. Each Supplier can have 1 or more FTP servers. We are going to download
Fetching Sponsored Content...
View First Topic Go to
Loading 1 - 15 of total 24,580 messages