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

View More author details

Table of Contents (21) Chapters

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

Why subscribe?

20. Other Books You May Enjoy

Running on-premises Mule runtime use cases

A Mule runtime can be set up on a single node or multiple nodes on-premises. Running a Mule runtime on a single node is not recommended if you are looking for better performance, high availability, and business continuity.

There are multiple ways you can set up the Mule runtime:

Runtime plane on-premises and no control plane
Runtime plane on-premises and control plane on Anypoint Platform
Runtime plane on-premises and control plane on Anypoint Platform PCE (fully on-premises)

Mule runtime plane on-premises and no control plane (standalone)

In this approach, the Mule runtime will be set up on-premises without registering the server to Anypoint Platform. This means we don’t have a control plane to manage the Mule runtime. With this approach, we will not be able to apply any API policies and cannot leverage Anypoint Monitoring for the application deployed to the Mule runtime on-premises. It is possible to cluster...