You're reading from MuleSoft Platform Architect's Guide A practical guide to using Anypoint Platform's capabilities to architect, deliver, and operate APIs

Product type Paperback

Published in Jul 2024

Publisher Packt

ISBN-13 9781805126188

Length 498 pages

Edition 1st Edition

Tools

Catalyst

Concepts

CRM

Authors (2):

Jim Andrews

Jitendra Bafna

Preface

1. Chapter 1: What is the MuleSoft Platform? FREE CHAPTER

2. Chapter 2: Platform Foundation Components and the Underlying Architecture

3. Chapter 3: Leveraging Catalyst and the MuleSoft Knowledge Hub

4. Chapter 4: An Introduction to Application Networks

5. Chapter 5: Speeding with Accelerators

6. Chapter 6: Aligning Desired Business Outcomes to Functional Requirements

7. Chapter 7: Microservices, Application Networks, EDA, and API-led Design

8. Chapter 8: Non-Functional Requirements Influence in Shaping the API Architecture

9. Chapter 9: Hassle-free Deployment with Anypoint iPaaS (CloudHub 1.0)

10. Chapter 10: Hassle-Free Deployment with Anypoint iPaaS (CloudHub 2.0)

11. Chapter 11: Containerizing the Runtime Plane with Runtime Fabric

12. Chapter 12: Deploying to Your Own Data Center

13. Chapter 13: Government Cloud and the EU Control Plane – Special Considerations

14. Chapter 14: Functional Monitoring, Alerts, and Operation Monitors

15. Chapter 15: Controlling API Sprawl with Universal API Management

16. Chapter 16: Addressing Non-Functional Requirements – from a Thought to an Operation

17. Chapter 17: Prepare for Success

18. Chapter 18: Tackling Tricky Topics

19. Index

20. Other Books You May Enjoy

Answers

Control Plane and Runtime plane are the two planes the Anypoint Platform operates on.
CloudHub, CloudHub 2.0, Runtime Fabric (RTF), Stand Alone servers are the current options for hosting the MuleSoft Runtime Plane.
Object Store v2 and Anypoint DataGraph are not available when running in RTF.
iPaaS is a comprehensive suite of cloud services enabling integration development and governance connecting on-premises applications and data with cloud-based processes, services, apps, and data. Point to point involves one application reaching into another application directly to collect data directly. RPC is a kind of point-to-point architecture that involves invoking remote calls in another application and getting data back. SOA is a service-oriented architecture without any globally agreed upon standards, which provides an approach to object interaction through predefined services.
Your answer should vary here depending on the experiences of your organization. I have seen organizations that had older mainframe systems with complex processing of overnight batch data. This of course impacts the ability to have a realtime view of data.