Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying MuleSoft Platform Architect's Guide
  • Table Of Contents Toc
  • Feedback & Rating feedback
MuleSoft Platform Architect's Guide

MuleSoft Platform Architect's Guide

By : Jitendra Bafna, Jim Andrews
5 (8)
close
close
MuleSoft Platform Architect's Guide

MuleSoft Platform Architect's Guide

5 (8)
By: Jitendra Bafna, Jim Andrews

Overview of this book

We’re living in the era of digital transformation, where organizations rely on APIs to enable innovation within the business and IT teams are asked to continue doing more with less. Written by Jim Andrews, a Mulesoft Evangelist, and Jitendra Bafna, a Senior Solution Architect with expertise in setting up Mulesoft, this book will help you deliver a robust, secure, and flexible enterprise API platform, supporting any required business outcome. You’ll start by exploring Anypoint Platform’s architecture and its capabilities for modern integration before learning how to align business outcomes with functional requirements and how non-functional requirements shape the architecture. You'll also find out how to leverage Catalyst and Accelerators for efficient development. You'll get to grips with hassle-free API deployment and hosting in CloudHub 1.0/2.0, Runtime Fabric Manager, and hybrid environments and familiarize yourself with advanced operating and monitoring techniques with API Manager and Anypoint Monitoring. The final chapters will equip you with best practices for tackling complex topics and preparing for the MuleSoft Certified Platform Architect exam. By the end of this book, you’ll understand Anypoint Platform’s capabilities and be able to architect solutions that deliver the desired business outcomes.
Table of Contents (21 chapters)
close
close

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

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY