Patterns, Principles, and Practices of Domain-Driven Design

13 Integrating via HTTP with RPC and REST

WHAT’S IN THIS CHAPTER?

• An introduction to the idea of using HTTP to integrate bounded contexts
• An introduction to the REST protocol
• Guidance for choosing between RPC and REST when integrating with HTTP
• DDD-focused examples of implementing RPC with SOAP and plain XML
• Examples of implementing RPC using WCF and ASP.NET Web API
• A discussion of how to use REST with DDD to achieve the fault tolerance and scalability of messaging systems while still being domain focused
• An example of building a scalable, fault-tolerant, event-driven, RESTful distributed system using ASP.NET Web API
• Guidance for enabling loosely coupled, independent teams when integrating bounded contexts with HTTP

Wrox.com Code Downloads for this 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 13 download and individually named according to the names throughout the chapter.

Hypertext Transport Protocol (HTTP) is a ubiquitous protocol that the billions of devices connected to the Internet understand. It can also be a discerning choice for integrating bounded contexts. Being so widespread, HTTP has clearly proven that it enables applications running on different hardware and software stacks to communicate relatively easily. This means that if you have bounded contexts using different technologies, HTTP can be very appealing. You saw in the previous chapter that ...