Aligning Desired Business Outcomes to Functional Requirements
A critical step in getting the most out of the MuleSoft platform is to understand the desired business outcomes and turn those outcomes into functional requirements. This chapter looks at how functional requirements line up with the platform’s capabilities. You will look at how these functional requirements can influence architecture decisions and design patterns such as data models, granularity, concurrency, and HTTP methods. The chapter will include examples of using bounded context data models versus Enterprise Data Models (EDMs).
In this chapter, we will cover the following topics:
- Developing business outcomes and functional requirements
- Designing for communication
- EDMs versus bounded context data models
- Coarse-grained versus fine-grained APIs
- API concurrency and HTTP verbs
- API callback
