MuleSoft Platform Architect's Guide : A Practical Guide to Using Anypoint Platform's Capabilities to Architect, Deliver, and Operate APIs

MuleSoft Platform Architect's Guide A Practical Guide to Using Anypoint Platform's Capabilities to Architect, Deliver, and Operate APIs

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,...

Descripción completa

Detalles Bibliográficos
Otros Autores: Bafna, Jitendra, author (author), Andrews, Jim, author
Formato: Libro electrónico
Idioma:Inglés
Publicado: Birmingham, England : Packt Publishing [2024]
Edición:First edition
Materias:
Application program interfaces (Computer software)
Computer software > Development.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009841734506719
Tabla de Contenidos:
  • 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&amp
  • 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&amp
  • 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).

Ejemplares similares