Patterns, Principles, and Practices of Domain-Driven Design

12 Integrating via Messaging

WHAT’S IN THIS CHAPTER?

• Integrating bounded contexts with asynchronous messaging using NServiceBus and Mass Transit
• Designing and modeling messaging systems around important events in the domain
• Understanding how messaging frameworks work
• Creating architectural diagrams
• Explanation of the conceptual differences between commands and events
• Theory and examples of industry-standard messaging patterns
• Dealing with eventual consistency
• Monitoring errors in messaging systems
• Monitoring service level agreements (SLAs) in messaging systems

Wrox.com Code Downloads for This Chapter

The wrox.com code downloads for this chapter are found at www.wrox.com/go/domaindrivendesign on the Download Code tab. The code is in the Chapter 12 download and individually named according to the names throughout the chapter.

Hopefully the concepts in the previous chapter got you excited about the prospect of building scalable distributed systems while still getting the full benefits of Domain-Driven Design (DDD). This chapter aims to provide you with the foundational skills you need so that you can immediately begin to apply those concepts to real systems. To acquire the necessary initial skills, you’re going to build an e-commerce messaging application using NServiceBus and Mass Transit. Along the way, you will see how to incorporate the knowledge you gain from domain experts into your model by using techniques that make domain concepts explicit in the code. You see how ...