Details

Subject(s)

• Application program interfaces (Computer software) [Browse]
• Computer software—Development [Browse]

Author

• Andrews, Jim [Browse]

Summary note

Unlock the power of Anypoint Platform by leveraging MuleSoft methodology, Accelerators, runtime engines, and management tools to deliver secure, high-value APIs and integration solutions across the enterprise Key Features Discover Anypoint Platform's capabilities for creating high-availability, high-performance APIs Learn about AnyPoint architecture and platform attributes for Mule app deployment Explore best practices, tips, and tricks that will help you tackle challenging exam topics and achieve MuleSoft certification Purchase of the print or Kindle book includes a free PDF eBook Book Description 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. As such, this book will help you deliver a robust, secure, and flexible enterprise API platform, supporting any required business outcome. You'll begin by understanding Anypoint Platform's architecture and its capabilities for a modern integration approach. Then, you'll learn how to align business outcomes with functional requirements and how non-functional requirements influence the shape of the architecture. You'll also explore how Catalyst and Accelerators can be leveraged successfully, enabling efficient development cycles. As you progress, you'll become familiar with hassle-free deployment and hosting APIs in CloudHub 1.0/2.0, Runtime Fabric Manager, and a hybrid customer-hosted environment. You'll discover advanced operating and monitoring techniques with API Manager and Anypoint Monitoring. The concluding chapters will offer guidance and best practices on how to tackle complex topics, which will also be useful in helping you pass the challenging 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. What you will learn Understand Anypoint Platform's integration architecture with core components Discover how to architect a solution using Catalyst principles Explore best practices to design an application network Align microservices, application networks, and event architectures with Anypoint Platform's capabilities Identify non-functional requirements that shape the architecture Perform hassle-free application deployment to CloudHub using the Mule Maven plugin, CLI, and Platform API Understand how to manage the API life cycle for MuleSoft and non-MuleSoft APIs Who this book is for This book is for technical and infrastructure architects with knowledge of integration and APIs who are looking to implement these solutions with MuleSoft's Anypoint Platform. Architects enrolled in the platform architect course who want to understand the platform's capabilities will also find this book helpful. The book is also a great resource for MuleSoft senior developers transitioning to platform architect roles and planning to take the MuleSoft Platform Architect exam. A solid understanding of MuleSoft API development, ideally 3 to 5 years of experience with the platform, is necessary.

Notes

Includes index.

Source of description

• Description based on publisher supplied metadata and other sources.
• Description based on print version record.

Contents

• 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
• 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
• Further reading
• 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
• 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
• Chapter 5: Speeding with Accelerators
• Unpacking the accelerator building blocks
• Pre-built APIs
• Connectors
• Templates
• 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
• 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
• 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
• 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
• Chapter 9: Hassle-free Deployment with Anypoint iPaaS (CloudHub 1.0)
• 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
• 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
• Chapter 10: Hassle-Free Deployment with Anypoint iPaaS (CloudHub 2.0)
• What is CloudHub 2.0?
• Why CloudHub 2.0?
• Replicas and replica size
• Clustering
• Application isolation
• Intelligent healing
• Zero-downtime updates
• Supported Mule runtime
• Granular vCore options
• Object Store v2
• 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
• Technical enhancements from CloudHub 1.0 to CloudHub 2.0
• Chapter 11: Containerizing the Runtime Plane with Runtime Fabric
• 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
• 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
• 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
• Internal service-to-service communication
• Persistence Gateway with Runtime Fabric
• Deployment strategy
• 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 benefits of Runtime Fabric
• Runtime Fabric on Red Hat OpenShift
• Chapter 12: Deploying to Your Own Data Center
• Hardware requirements
• Software requirements
• Why an on-premises Mule runtime?
• Running applications in an on-premises Mule runtime
• 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).

Show 260 more Contents items

ISBN

9781805129622 ((electronic bk.))

OCLC

1450431535

Statement on language in description

Princeton University Library aims to describe library materials in a manner that is respectful to the individuals and communities who create, use, and are represented in the collections we manage. Read more...