Depending on who is on the team, different teams tend to use slightly different language to describe the same thing.

For a team that's in shipping, it's a thing that goes in a box that goes from one place to the other. For a person that's in inventory, it's a thing whether you have or you don't have, and that's their concern. For them, the important thing is how can they market it.

For a person in sales, it's a thing that is marketable, that sells. The definition of what a product could depend on who you ask. This is years and years of practice, and we try to look at all the data that goes together, and we come up with this model. If we wanted to model this in our software, we tend to have a model for it. We see pictures, name, description, price, and so on. If we look at trying to model this page, we see a lot of things. My kids presented me an iPhone cell phone case for Christmas.

My family and I, we buy iPhone cases because I am the iPhone killer of the family. That's how I started getting into event-driven architecture to see how to scale, and that led me on a journey of event-driven architecture. You can understand why, because in 2010 is when the real estate meltdown happened and the core business was about sending all these regulatory notices, and so the software couldn't keep up with the load. Business was ok, but in 2010, the software couldn't keep up with the load. They did this on behalf of banks and mortgage companies. For me, combining the domain-driven-design discipline and the event-driven architecture as a technology gives you the best of both worlds.īefore I started particular software, several years ago, I worked for this company, and the core domain of this company was sending regulatory notices when homeowners defaulted on their mortgage payments. To me, the whole deal of trying to have small services is so they could be autonomous, so you can scale, so they can be reliable, and so on. For me, event-driven architecture and domain-driven design are awesome things, and when you put those two awesome things together, you can get really cool services that are autonomous. NET that enables event-driven architecture, and it's built on top of existing queuing technologies like RabbitMQ, Azure Service Bus, and so on. Alagarsamy: For those of you who don't know NServiceBus, it's a messaging platform, a software for.

Distributed domain driven design