MuleSoft Platform Architect's Guide
A practical guide to using Anypoint Platform's capabilities to architect, deliver, and operate APIs
1. Auflage
Erschienen am 18. März 2025
498 Seiten
978-1-80512-962-2 (ISBN)
Beschreibung
No detailed description available for "MuleSoft Platform Architect's Guide".
Alle Preise
Weitere Details
Weitere Ausgaben
Personen
Bafna Jitendra :
Jitendra Bafna is a Senior Solution Architect and expert with vast experience in designing and solutioning the integrations and APIs solutions. He is a TOGAF 9.2 Level 1 and Level 2 certified and has expertise in various integration platforms. Jitendra has expertise in architecting and setting up MuleSoft Platform including CloudHub, CloudHub 2.0, Runtime Fabric, Hybrid, Flex Gateway, and Customer Hosted Platform. He completed his Bachelor of Engineering in Computer Science from Mumbai University and a Certificate Programme in Digital Transformation and Innovation from Indian Institute of Management Indore (IIM-I) in 2023.Andrews Jim :
Jim Andrews is an Integration Architecture Specialist, a MuleSoft evangelist, and a life-long learner: He has been designing and building integration solutions for dozens of clients for over 30 years in an ever-evolving technical landscape. A student of architectural methods, he holds TOGAF 9 Level 1 & 2 certifications. As a volunteer for the MuleSoft certification team, Jim helped develop exams for MuleSoft Developer L2, Integration Associate, Integration and Platform Architecture. A member of the MuleSoft Developer Community and Houston Meetup Leader, Jim presents at Meetups, Dreamforce, and Salesforce TDX. In his spare time, he co-hosts the podcast Bits Th at Bind. Jim holds BSc degree in a Computer Information Systems from Tarleton State University.
Jitendra Bafna is a Senior Solution Architect and expert with vast experience in designing and solutioning the integrations and APIs solutions. He is a TOGAF 9.2 Level 1 and Level 2 certified and has expertise in various integration platforms. Jitendra has expertise in architecting and setting up MuleSoft Platform including CloudHub, CloudHub 2.0, Runtime Fabric, Hybrid, Flex Gateway, and Customer Hosted Platform. He completed his Bachelor of Engineering in Computer Science from Mumbai University and a Certificate Programme in Digital Transformation and Innovation from Indian Institute of Management Indore (IIM-I) in 2023.Andrews Jim :
Jim Andrews is an Integration Architecture Specialist, a MuleSoft evangelist, and a life-long learner: He has been designing and building integration solutions for dozens of clients for over 30 years in an ever-evolving technical landscape. A student of architectural methods, he holds TOGAF 9 Level 1 & 2 certifications. As a volunteer for the MuleSoft certification team, Jim helped develop exams for MuleSoft Developer L2, Integration Associate, Integration and Platform Architecture. A member of the MuleSoft Developer Community and Houston Meetup Leader, Jim presents at Meetups, Dreamforce, and Salesforce TDX. In his spare time, he co-hosts the podcast Bits Th at Bind. Jim holds BSc degree in a Computer Information Systems from Tarleton State University.
Inhalt
- Cover
- Title Page
- Copyright and Credits
- Contributors
- Table of Contents
- Preface
- Chapter 1: What is the MuleSoft Platform?
- Technical requirements
- What is MuleSoft and iPaaS?
- How have integration approaches evolved?
- J&J Music Store Use Case
- Point to Point
- Middleware and Remote Procedure Calls
- Enterprise Service Bus
- Service Oriented Architecture
- Representational State Transfer (REST Services)
- iPaaS
- What is the modern challenge to integration?
- Breaking the law is harder than you think
- Business innovation at the speed of technical debt
- The Architectural capabilities of MuleSoft
- Planes of operations
- Platform deployment options
- MuleSoft capabilities and components
- Why are APIs so important in delivering modern integrations?
- Summary
- Questions
- Answers
- Further Reading
- Chapter 2: Platform Foundation Components and the Underlying Architecture
- Technical requirements
- The Anypoint control plane
- Control plane hosting options
- Securing the Anypoint control plane
- Organizing the Anypoint control plane
- The runtime plane overview
- Runtime deployment options
- Runtime plane hosting
- Core components in the runtime plane
- Combining control plane hosts and runtime hosts
- Anypoint Core Services
- Management capability
- Design capability
- Discover Capability
- Summary
- Questions
- Further reading
- Answers
- Chapter 3: Leveraging Catalyst and the MuleSoft Knowledge Hub
- Exploring Catalyst, its core principles, and its engagements
- What is Catalyst?
- Catalyst's foundation
- Playbook organization
- Catalyst engagements
- Leveraging the Catalyst Knowledge Hub
- Finding value in a C4E
- Team enablement
- Metrics and KPIs
- Staffing
- Summary
- Questions
- Further reading
- Answers
- Chapter 4: An Introduction to Application Networks
- An introduction to MuleSoft application networks
- What is an application network?
- Components and the importance of an application network
- Building and implementing an application network
- Planning the roadmap
- Designing and developing
- Managing and evangelizing reuse
- The benefits and best practices of an application network
- Benefits
- Best practices
- Summary
- Questions
- Further reading
- Answers
- Chapter 5: Speeding with Accelerators
- Unpacking the accelerator building blocks
- Pre-built APIs
- Connectors
- Templates
- Best practices
- Data mappings
- Endpoints
- Customizing MuleSoft accelerators
- Customizing the Accelerator for Retail - J&J Music Store speeds up
- Essential building blocks for MuleSoft accelerators
- The MuleSoft Catalyst GitHub repository
- Summary
- Further reading
- Chapter 6: Aligning Desired Business Outcomes to Functional Requirements
- Developing business outcomes and functional requirements
- Designing for communication
- EDM
- Advantages of an EDM
- Disadvantages of EDMs
- Bounded context data model
- Advantages of the bounded context data model
- Disadvantages of the bounded context data model
- Coarse-grained APIs
- Advantages of coarse-grained APIs
- Disadvantages of coarse-grained APIs
- Fine-grained APIs
- Advantages of fine-grained APIs
- Disadvantages of fine-grained APIs
- API concurrency
- HTTP verbs
- API callback
- Summary
- Chapter 7: Microservices, Application Networks, EDA, and API-led Design
- Monolithic architecture
- Advantages of a monolithic architecture
- Disadvantages of a monolithic architecture
- Microservices architecture
- Characteristics of microservices
- Advantages of a microservices architecture
- Disadvantages of a microservices architecture
- Saga pattern
- Saga choreography pattern
- Saga orchestration pattern
- The Competing Consumers pattern
- Benefits of implementing the Competing Consumers pattern
- Circuit Breaker pattern
- Circuit Breaker states
- Anypoint MQ
- Message exchanges and queues
- Cross-region failover for Anypoint MQ standard queues
- Dead-letter queues
- The Circuit Breaker pattern with Anypoint MQ
- Event-driven architecture (EDA)
- Benefits of EDA
- Limitations of EDA
- API-led connectivity and EDA together
- Experience API
- Process API
- System API
- Application networks and composability
- Summary
- Chapter 8: Non-Functional Requirements Influence in Shaping the API Architecture
- Common non-functional requirements
- Meeting performance requirements in the platform
- Response time
- Throughput
- Error rates
- Availability
- Latency
- Scalability
- Resource allocation
- Performance testing
- Performance monitoring
- Load balancing
- Application caching
- API security
- Data security in motion or in transit
- Data security at rest
- Deployment strategies
- Rolling update deployment
- Blue-green deployment
- Canary deployment
- Summary
- Further reading
- Chapter 9: Hassle-free Deployment with Anypoint iPaaS (CloudHub 1.0)
- Technical requirements
- What is CloudHub 1.0?
- Workers and worker size
- Shared load balancer
- Region
- DNS records
- Intelligent healing (single-region disaster recovery)
- Zero downtime updates
- High availability
- Scalability
- Persistent Queues
- Managing schedules
- Object Store V2
- Static IP address
- Anypoint VPC
- Anypoint VPC architecture
- VPN IPsec tunnels
- VPC peering
- Transit Gateway Attachments
- AWS Direct Connect
- Calculating a CIDR mask for Anypoint VPC
- Anypoint dedicated load balancer
- Allowlist CIDRs
- SSL certificates
- Mutual authentication
- Dedicated load balancer sizing
- Dedicated load balancer timeout
- Dedicated load balancer mapping rules
- HTTP inbound mode
- Recommendations
- Dedicated load balancers for public and private traffic
- Different options for deploying a MuleSoft application to CloudHub 1.0 Runtime Manager
- The Mule Maven plugin
- Anypoint CLI
- CloudHub 1.0 API
- Summary
- Further reading
- Chapter 10: Hassle-Free Deployment with Anypoint iPaaS (CloudHub 2.0)
- What is CloudHub 2.0?
- Why CloudHub 2.0?
- Replicas and replica size
- Region
- Clustering
- High availability
- Application isolation
- Intelligent healing
- Zero-downtime updates
- Scalability
- Supported Mule runtime
- Granular vCore options
- Object Store v2
- Managing schedules
- Last-mile security
- Shared space
- Private space
- AWS service role
- Inbound and outbound traffic rules
- TLS context and domains
- Public and private endpoints
- Ingress load balancer
- HTTP requests
- VPN connection
- Transit gateways
- Private space network architecture
- Multiple environments in private spaces
- Multiple domains in private spaces
- Different options for deploying MuleSoft applications to CloudHub Runtime Manager
- Anypoint CLI
- Technical enhancements from CloudHub 1.0 to CloudHub 2.0
- Summary
- Further reading
- Chapter 11: Containerizing the Runtime Plane with Runtime Fabric
- Technical requirements
- Kubernetes architecture
- Master node components
- Worker node components
- What is Runtime Fabric?
- Runtime Fabric on bare-metal servers/VMs
- Network architecture
- Shared responsibility between the customer and MuleSoft
- The concept of etcd in Runtime Fabric
- Quorum management
- Scalability
- High availability
- Fault tolerance
- Inbound load balancer (ingress load balancer)
- Anypoint Security
- Application performance metrics
- Internal load balancer performance metrics
- Runtime Fabric on self-managed Kubernetes
- Runtime Fabric architecture on EKS
- Installing Runtime Fabric on self-managed Kubernetes
- Shared responsibilities between the customer and MuleSoft
- High availability and fault tolerance
- Scalability
- How will an application deployed to self-managed Kubernetes communicate with an external service for which IP whitelisting is required?
- The difference between Runtime Fabric on self-managed Kubernetes and bare-metal/VMs
- Tokenization services
- Secrets Manager
- CPU bursting in Runtime Fabric
- Pod
- Last-mile security
- Internal service-to-service communication
- Persistence Gateway with Runtime Fabric
- Deployment strategy
- Clustering
- Backing up and restoring Runtime Fabric
- When to use the backup and restore process
- What's backed up?
- Backing up and restoring
- Different options for deploying a MuleSoft application to Runtime Fabric
- The Mule Maven plugin
- The benefits of Runtime Fabric
- Runtime Fabric on Red Hat OpenShift
- Summary
- Chapter 12: Deploying to Your Own Data Center
- Technical requirements
- Hardware requirements
- Software requirements
- Why an on-premises Mule runtime?
- Running applications in an on-premises Mule runtime
- High availability
- Scalability
- Load balancer
- Anypoint clustering
- Concurrency issues
- Setting up Anypoint clustering manually
- Setting up Anypoint clustering on Anypoint Platform
- Persistent object store
- Primary node and secondary nodes
- VM queues in Anypoint clustering
- Anypoint server group
- Anypoint Platform Private Cloud Edition
- Running on-premises Mule runtime use cases
- Mule runtime plane on-premises and no control plane (standalone)
- Mule runtime plane on-premises and control plane on Anypoint Platform (hybrid)
- Mule runtime plane on-premises and control plane on Anypoint Platform PCE (fully on-premises)
- Running multiple MuleSoft applications on a single port (Mule domain)
- How to use a domain project in API-led connectivity architecture
- Deploying a MuleSoft application on-premises using the Mule Maven plugin
- Deploying a MuleSoft application on-premises using the Anypoint Runtime Manager (ARM) REST API
- Deploying Mule for high availability and disaster recovery strategies
- Cold standby
- Warm standby
- Hot standby - active-passive
- Active-active
- Upgrading a Mule runtime or scaling the underlying infrastructure without any downtime
- Mule runtime on-premises security
- Summary
- Further reading
- Chapter 13: Government Cloud and the EU Control Plane - Special Considerations
- FedRAMP compliance
- What is MuleSoft Government Cloud?
- Government Cloud considerations
- Security in MuleSoft Government Cloud
- Anypoint Virtual Private Cloud and Virtual Private Network in MuleSoft Government Cloud
- A dedicated load balancer in MuleSoft Government Cloud
- The MuleSoft Government Cloud control plane
- The MuleSoft Government Cloud runtime plane
- Standalone Mule support in MuleSoft Government Cloud
- Deployment models for MuleSoft Government Cloud
- The EU control plane
- EU control plane considerations
- Deploying applications to the EU control plane
- Object Store in the EU control plane
- Moving from the US control plane to the EU control plane
- Anypoint VPC and VPN in the EU control plane
- Anypoint Dedicated Load Balancer (DLB) in the EU control plane
- Summary
- Further reading
- Chapter 14: Functional Monitoring, Alerts, and Operation Monitors
- Why is API monitoring required?
- Anypoint Monitoring
- The monitoring and analytics capabilities of Anypoint API Manager
- Understanding Mule API analytics charts
- API Manager alerts
- Understanding the Mule Analytics Event API
- API reports
- Understanding Anypoint Monitoring
- Dashboards
- Anypoint Monitoring event-driven alerts
- Enabling Anypoint Monitoring for applications deployed to CloudHub
- Enabling Anypoint Monitoring for applications deployed to CloudHub 2.0
- Enabling Anypoint Monitoring for applications deployed to Runtime Fabric
- Enabling Anypoint Monitoring for applications deployed in hybrid environments
- Data retention policy and limits
- Monitoring connectors
- Server information for hybrid environments
- Enabling alerts for hybrid environments with Runtime Manager
- Enabling alerts for CloudHub with Runtime Manager
- Enabling alerts for CloudHub 2.0 with Runtime Manager
- Functional Monitoring
- Monitoring the endpoints of public APIs
- Monitoring the endpoints of private APIs
- Why is logging important?
- Logs in Anypoint Monitoring
- Understanding logging with MuleSoft applications deployed to CloudHub
- Understanding logging with MuleSoft applications deployed to CloudHub 2.0
- Understanding logging with MuleSoft applications deployed to on-premises/hybrid environments
- Understanding logging with MuleSoft applications deployed to Runtime Fabric on bare-metal systems/VMs
- JSON logging with a Mule application
- Anypoint Visualizer
- Summary
- Further reading
- Chapter 15: Controlling API Sprawl with Universal API Management
- API sprawl
- How to prevent API sprawl
- Universal API management
- API management
- The full API management life cycle
- API gateway
- Mule Gateway
- API proxies
- When to use an API proxy
- API proxies versus API autodiscovery
- Anypoint Service Mesh
- Benefits of Flex Gateway
- Flex Gateway in Connected Mode
- Flex Gateway in Local Mode
- Flex Gateway deployment models
- High availability and scalability with Flex Gateway
- Routing in Flex Gateway
- Flex Gateway in Centralized Mode
- Flex Gateway in Decentralized Mode
- Flex Gateway API policies
- Flex Gateway versus Mule Gateway
- Share and discover APIs using Anypoint Platform
- Developer portal
- ACM
- API Experience Hub
- ACM versus API Experience Hub
- API Analytics
- API policies
- API Governance
- Implementing API Governance
- Anypoint API Manager alerts
- API security threats
- DoS
- Summary
- References
- Chapter 16: Addressing Non-Functional Requirements - from a Thought to an Operation
- Prerequisites
- What are NFRs?
- High availability
- High availability and fault tolerance with CloudHub 1.0
- High availability and fault tolerance with CloudHub 2.0
- High availability and fault tolerance with the on-premises Mule runtime
- High availability and fault tolerance with Runtime Fabric (bare-metal servers/VMs)
- High availability and fault tolerance with Runtime Fabric (self-managed Kubernetes)
- Scalability
- Scalability with CloudHub 1.0
- Scalability with CloudHub 2.0
- Scalability with Runtime Fabric (bare-metal servers/VMs)
- Scalability with Runtime Fabric (self-managed Kubernetes)
- DR
- DR for CloudHub 1.0 (multi-region)
- DR for CloudHub 2.0 (multi-region)
- DR for the on-premises Mule runtime
- vCores allocation and optimization
- vCores optimization and allocation with CloudHub 1.0 and CloudHub 2.0
- vCores optimization and allocation with the on-premises Mule runtime
- vCores optimization and allocation with Runtime Fabric
- Summary
- Chapter 17: Prepare for Success
- MCPA - Level 1 certification
- Format of the examination
- Validity
- MCPA - Level 1 Maintenance exam
- How to prepare for MCPA - Level 1
- Why take the MCPA - Level 1 exam?
- Who should take the MCPA - Level 1 exam?
- What topics are covered in the examination?
- Strategies for answering multiple-choice questions
- System requirements for the examination
- Exam day
- Summary
- Questions
- Further reading
- Answers
- Chapter 18: Tackling Tricky Topics
- Considerations for choosing the right deployment model
- CloudHub 1.0
- CloudHub 2.0
- Runtime Fabric
- On-premises Mule runtime
- Anypoint CLI
- Resilient API techniques
- Idempotent scope
- Cache scope
- Core components
- Choice router
- Scatter-Gather router
- Error handling
- Transform Message
- Use case 1
- Use case 2
- Use case 3
- Summary
- Index
- Other Books You May Enjoy
