Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 32 Anzeige

MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options

Herunterladen, um offline zu lesen

MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options

MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options

Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options (20)

Anzeige

Weitere von Jitendra Bafna (20)

Aktuellste (20)

Anzeige

MuleSoft Surat Virtual Meetup#16 - Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options

  1. 1. [Surat] MuleSoft Meetup Group Anypoint Deployment Option, API and Operational Capabilities and Disaster Recovery Options 1st May 2021
  2. 2. 2 Organizers Jitendra Bafna Senior Solution Architect Capgemini About the organizer: ➢ Working as Senior Solution Architect at Capgemini. ➢ MuleSoft Ambassador ➢ Surat MuleSoft Meetup Leader. ➢ 12.5+ Years of Experience in Integrations and API Technologies. ➢ Certified MuleSoft Integration Architect and platform Architect.
  3. 3. 3 Organizers Nitish Jain Consultant IBM About the organizer : ➢ Working as Consultant at IBM. ➢ Surat MuleSoft Meetup Leader. ➢ 2.5+ Years of Experience in Integrations and API Technologies. ➢ Certified MuleSoft Developer and Platform Architect.
  4. 4. 4 Speakers Jitendra Bafna Senior Solution Architect Capgemini About the speaker: ➢ Working as Senior Solution Architect at Capgemini. ➢ MuleSoft Ambassador ➢ Surat MuleSoft Meetup Leader. ➢ 12.5+ Years of Experience in Integrations and API Technologies. ➢ Certified MuleSoft Integration Architect and platform Architect.
  5. 5. CHEERS..!! We have prizes to give away! 3 Winners a special prize is ready 5 A SHOW OF HANDS: New Members With Us.!!
  6. 6. Agenda MuleSoft and its History MuleSoft Operational and API Capabilities Use Case 1: CloudHub Architecture Use Case 2: CloudHub Architecture With VPC, VPN and DLB Use Case 3: Customer Hosted Mule Runtime (Hybrid) Use Case 4: Runtime Fabric Manager Use Case 5: API Management Capabilities for Non Mule Application Trivia Quiz 1 2 3 4 5 6 7 8
  7. 7. MuleSoft in Gartner Magic Quadrant - 2020 Gartner has recognized the company as a Leader for the sixth time in the 2020 Magic Quadrant for Enterprise Integration Platform as a Service (iPaaS). In addition, MuleSoft has been named a Leader for the fifth consecutive time in the 2020 Gartner Magic Quadrant for Full Life Cycle API Management
  8. 8. What is MuleSoft? MuleSoft is the software company having headquartered in the San Francisco, California that provides the integration software to connect applications, data or devices etc. Founded as a MuleSource by Ross Mason and Dave Rosenberg. MuleSource has been renamed to MuleSoft. MuleSoft originally provided Messaging and Middleware capabilities, later expanded to IPaaS through product Anypoint Platform. 2006 2009 2013 2016 MuleSoft acquired the ProgrammableWeb. MuleSoft was ranked #20 on the Forbes Cloud 100 list. MuleSoft filed the IPO and start trading in New York Stock Exchange. 2017 2018 MuleSoft acquired by Salesforce.
  9. 9. Design Center Design Center provides tools to design the APIs, developer Connectors and MuleSoft Applications. RAML is used to design the APIs. Anypoint Exchange Anypoint Exchange is repository hub where you can store your reusable assets and search for connectors, public or private assets. Runtime Manager Runtime Manager is the place where you can deploy and manage the MuleSoft Application. It also provide capabilities to setup Anypoint Virtual Private Cloud, Virtual Private Network and Dedicated Load Balancer. API Manager API Manager is the component of the Anypoint Platform for managing the lifecycle of API and secure the APIs using policies. This component basically governed the APIs. Access Management This component is basically used to manager users, subscriptions, roles, organization, environments, Identity Management etc. Workers are dedicated instances of Mule runtime engine that run your integration applications on CloudHub. Worker sizes have different compute, memory, and storage capacities. Worker and Worker Size Worker Size Heap Memory Storage 0.1 vCores 500 MB 8 GB 0.2 vCores 1 GB 8 GB 1 vCore 1.5 GB 12 GB 2 vCores 3.5 GB 40 GB 4 vCores 7.5 GB 88 GB 8 vCores 15 GB 168 GB 16 vCores 32 GB 328 GB Horizontal and Vertical Scaling In CloudHub, Horizontal Scaling can easily done by increasing the number of workers. Vertical scaling can be achieved by increasing the vCores size. Auto Scaling CloudHub allows you to make the processing power behind your applications responsive to changes in their usage. You can define policies that respond to CPU or memory usage thresholds by scaling up or scaling down the processing resources used by an application. Intelligent Healing CloudHub monitors the worker clouds for problems and provides a self-healing mechanism to recover from them. If the underlying hardware suffers a failure, the platform migrates your application to a new worker automatically. Zero-Downtime Updates CloudHub supports updating your applications at runtime so end users of your HTTP APIs experience zero downtime. While your application update is deploying, CloudHub keeps the old version of your application running. Your domain points to the old version of your application until the newly uploaded version is fully started. MuleSoft Anypoint Platform (Cloudhub) Components and Capabilities
  10. 10. MuleSoft Region and Multitenancy 10 US East (N. Virginia) US East (Ohio) US West (N. California) EU (Ireland) EU (London) EU (Frankfurt) Asia Pacific (Tokyo) Asia Pacific (Singapore) Asia Pacific (Sydney) Central (Canada) South America (Sao Paulo) Runtime Manager (CloudHub) Region Sub-Domain US East (North Virginia) us-e1.cloudhub.io US East (Ohio) us-e2.cloudhub.io US West (Oregon) us-w2.cloudhub.io US West (North California) us-w1.cloudhub.io Canada (Central) ca-c1.cloudhub.io Brazil (Sao Paulo) br-s1.cloudhub.io Europe (Ireland) ir-e1.cloudhub.io Europe (Frankfurt) de-c1.cloudhub.io UK (London) uk-e1.cloudhub.io Asia Pacific (Tokyo) jp-e1.cloudhub.io Asia Pacific (Sydney) au-s1.cloudhub.io Asia Pacific (Singapore) sg-s1.cloudhub.io US West (Oregon) ➢ First, the worker cloud is a multitenant cloud of virtual machines. These VMs provide the security and isolation needed for your integrations to run custom code without affecting others. ➢ Second, the management console and the platform services have a "shared everything" architecture – all tenants share the same web UI, monitoring services, load balancers, etc. These services do not process or transmit your data.
  11. 11. MuleSoft Operational Capabilities and Deployment Options
  12. 12. Use Case 1: CloudHub Architecture 12 Problem Statement: ● Client is looking to implement MuleSoft for connecting SaaS applications like Salesforce, Netsuite etc. ● Cloud based solution where they don’t want to manage infrastructure and all applications must be highly available and fault tolerance. ● API must be secured with Client Id Enforcement policies. ● Platform must have feature like Intelligent healing, Zero Down Time updates.
  13. 13. Use Case 1: CloudHub Architecture - Solution 13 SaaS Apps (Salesforce/Netsuite /Databases) Runtime Manager Dev Test Prod Platform Services Worker Worker Worker Worker Worker Worker Worker Worker Worker Worker Worker Worker Logs Insights Scheduler Management Alerts Application Data API Manager API Policies/Security API Gateway API Analytics API Alerts and Monitoring Public Internet API Proxy/API Auto Discovery Anypoint Platform Client
  14. 14. Use Case 2: CloudHub Architecture (Accessing Application Within Private DC or Cloud) 14 Problem Statement: ● Client is looking to implement MuleSoft for connecting SaaS applications like Salesforce, SAP system in private AWS cloud and Databases and resources in on premise system. ● Cloud based solution where they don’t want to manage infrastructure and all applications must be highly available and fault tolerance. ● Application can be access by fewer client publicly. ● API must be secured with OAuth JWT. ● Platform must have feature like Intelligent healing, Zero Down Time updates.
  15. 15. Use Case 2: CloudHub Architecture (Accessing Application Within Private DC or Cloud) - Solution 15 SaaS Apps (Salesforce/Netsuite /Databases) Platform Services Logs Insights Scheduler Management Alerts Application Data API Manager API Policies/Security API Gateway API Analytics API Alerts and Monitoring API Proxy/API Auto Discovery Anypoint Platform Client Runtime Manager Non Prod VPC (10.0.1.0/22) Prod VPC (192.168.1.0/22) Dedicated Load Balancer (Prod) Dedicated Load Balancer (Non Prod) Dev Test Prod Databases Databases Core Systems Core Systems VPN IPSec Tunnelling VPN IPSec Tunnelling Corporate Datacenter (Non Prod) Corporate Datacenter (Prod) us-east-1 us-east-1 AWS Cloud DC (us-east-1) AWS Resources (Prod) 172.168.1.0/16 AWS Resources (Non Prod) 11.0.1.0/16
  16. 16. Use Case 3: Customer Hosted MuleSoft Runtime (Hybrid Implementation) - Clustering 16 Problem Statement: ● Financial institution is looking to implement cost effective solution and can operate on minimal cores. Solution must be highly available and having low workloads. ● Due to compliance or security requirements within organization, they cannot move to cloud based approach. ● API must be secured with Client Id Enforcement policy. ● Application deployed on Mule Runtime must be highly available. ● Need to support integration with HTTP Listener, JMS Topic and Queue Listener, File Listener, SAP Listener. Data needs to shared across the node.
  17. 17. Use Case 3: Customer Hosted MuleSoft Runtime (Hybrid Implementation) - Solution 17 Prod Server 1 (Mule Runtime 4.3) Prod Server 2 (Mule Runtime 4.3) Test Server 1 (Mule Runtime 4.3) Test Server 2 (Mule Runtime 4.3) Prod Environment Clustering Test Environment Clustering Prod Load Balancer Test Load Balancer Customer Hosted (Data Plane) Behind Firewall https 443 https 443 https 443 https 443 Distributed Memory Grid Distributed Memory Grid API Manager API Policies API Analytics API Security API Auto Discovery/API Proxy Anypoint Platform (Control Plane) Anypoint Monitoring and Alerts
  18. 18. Use Case 4: Customer Hosted MuleSoft Runtime (Hybrid Implementation) – Server Group 18 Problem Statement: ● Financial institution is looking to implement cost effective solution and can operate on minimal cores. Solution must be highly available and having low workloads. ● Due to compliance or security requirements within organization, they cannot move to cloud based approach. ● API must be secured with Client Id Enforcement policy. ● Application deployed on Mule Runtime must be highly available. ● Need to support integration with HTTP Listener and JMS Queue Listener. No need of data sharing.
  19. 19. Use Case 4: Customer Hosted MuleSoft Runtime (Hybrid Implementation) - Solution 19 Prod Server 1 (Mule Runtime 4.3) Prod Server 2 (Mule Runtime 4.3) Test Server 1 (Mule Runtime 4.3) Test Server 2 (Mule Runtime 4.3) Prod Environment Server Group Test Environment Server Group Prod Load Balancer Test Load Balancer Customer Hosted (Data Plane) Behind Firewall https 443 https 443 https 443 https 443 API Manager API Policies API Analytics API Security API Auto Discovery/API Proxy Anypoint Platform (Control Plane) Anypoint Monitoring and Alerts
  20. 20. Use Case 5: Customer Hosted - Runtime Fabric Manager 20 Problem Statement: ● Client is looking to implement cost effective solution and can operate on minimal cores. ● Solution must be highly available, fault tolerant and having moderate workloads. ● They want to migrate all the 400+ integration to MuleSoft and able to assign minimum unit of core while deploying applications. ● Client is looking for container based solution. ● API must be secure at Edge and application level by applying policies like Rate Limiting, Client Id Enforcement.
  21. 21. Use Case 5: Customer Hosted - Runtime Fabric Manager - Solution 21 Customer Hosted (Data Plane) Customer Hosted (Data Plane) API Manager API Policies API Analytics API Security Anypoint Platform (Control Plane) Anypoint Monitoring and Alerts Mule Runtime Application Mule Runtime Application Mule Runtime Application Agent Internal Load Balancer Agent Internal Load Balancer Agent Internal Load Balancer Mule Runtime Application Mule Runtime Application Mule Runtime Application Worker 1 Worker 2 Worker 3 Controller Controller Controller Anypoint Security https 443 Behind Firewall TCP Load Balancer API Auto Discovery/API Proxy
  22. 22. Use Case 6: Leverage Anypoint API Management Capabilities for Non MuleSoft Application 22 Problem Statement: ● Client wants to implement API Management Capabilities for Non MuleSoft applications. ● Having ‘n’ number of web services and apis implemented using non mule technologies but there is no capabilities of API governance. ● Need to enable OAuth 2.0 Authentication for all the web services and apis. ● Want fewer clients can access apis publicly and securely. ● Non MuleSoft
  23. 23. Use Case 6: Leverage Anypoint API Management Capabilities for Non MuleSoft Application - Solution 23 Web Services Non MuleSoft APIs On Premise VPN Anypoint VPN VPN IPSec Tunnelling Behind Firewall On Premise Mule Proxy 1 Mule Proxy 2 Mule Proxy 3 Mule Proxy 4 Mule Proxy 5 Anypoint VPC (10.0.1.0/24) API Policies API Security API Analytics API Alerts and Monitoring
  24. 24. 24 Disaster Recovery – Single Worker •Application will be deployed to one availability zone out of three in selected AWS region. •In case of AZ failure or unavailable, MuleSoft will automatically restarts application in other AZ. It may experiences some downtime. •Set up status.mulesoft.com to receive alerts in case of anything fails in AZ. •Distance between each AZ is variable and not exceeded 350 miles.
  25. 25. 25 Disaster Recovery – Multiple Worker • Application will be deployed to two availability zone out of three in selected AWS region. • In case of one AZ failure, all request will be served by other application deployed on other AZ. No downtime experiences. • Set up status.mulesoft.com to receive alerts in case of anything fails in AZ.
  26. 26. 26 Runtime Manager Runtime Manager us-east-1 us-east-2 Dedicated Load Balancer Dedicated Load Balancer Dedicated Load Balancer Dedicated Load Balancer External Load Balancer (Prod) Non-Prod VPC Prod VPC Prod VPC Non-Prod VPC W W W W W W W W QA Dev W W W W W W W W Test Dev Prod W W W W W W W W Prod W W W W W W W W SaaS Apps/Apps Accessible over Internet Corporate Datacenter (Prod) Backend Services External Load Balancer (Non-Prod) Disaster Recovery – Multi Region
  27. 27. Get ready to WIN a Special Gift from MuleSoft Community Quiz Time
  28. 28. Question 1 What is best way to connect AWS VPC and Anypoint VPC if they exists in same region? a. VPC Peering b. VPN IP Sec Tunneling c. Direct Connect d. None of the Above 28
  29. 29. Question 2 Can we implement Clustering in CloudHub? a. True b. False 29
  30. 30. Question 3 How to enable API Management capabilities for Non Mule Application? a. API Auto Discovery b. API Proxy c. API Analytics d. API Security 30
  31. 31. 31 Share: ○ Tweet your pictures using the hashtag #SuratMuleSoftMeetup ○ Invite your network to join: https://meetups.mulesoft.com/surat/ Feedback: ○ Fill out the survey feedback and suggest topics for upcoming events ○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program ○ Reach out to either Jitendra Bafna or Nitish Jainto suggest topics for next Meetup What’s next?
  32. 32. Thank you

×