Anypoint Platform Deployment Strategies
•Télécharger en tant que PPTX, PDF•
0 j'aime•2,170 vues
Various Mule ESB deployment strategies
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (11)
Similaire à Anypoint Platform Deployment Strategies
Similaire à Anypoint Platform Deployment Strategies (20)
Dernier
Dernier (20)
Anypoint Platform Deployment Strategies
- 2. 2015 © WHISHWORKS. All rights reserved. WHISHWORKS Confidential Pure On-premise Mule ESB Server Cluster Mule MMC Firewall / Load balancer Mule ESB Server Cluster Load balancer Anypoint API Web Management Console API Anypoint API Implementation Apps Anypoint API Proxy Apps LAN DMZ
- 3. 2015 © WHISHWORKS. All rights reserved. WHISHWORKS Confidential Hybrid API Mule ESB Server Cluster Mule MMC Anypoint API Web Management Console Anypoint API Implementation Apps Anypoint API Proxy Apps LAN Internet Load balancer Firewall / Load balancer Secure via VPC, 2-way SSL of fixed IP API Gateway Runtime
- 4. 2015 © WHISHWORKS. All rights reserved. WHISHWORKS Confidential CloudHub with VPC API Internal Systems LANVPC Anypoint API Web Management Console Anypoint API Proxy Apps Internet Anypoint API Implementation Apps API Gateway Runtime
- 5. 2015 © WHISHWORKS. All rights reserved. WHISHWORKS Confidential Cloudhub without VPC API Internal Systems Anypoint API Web Management Console API Apps Direct Implementation LAN Internet API Gateway Runtime Firewall Secure via VPC, 2-way SSL of fixed IP
Notes de l'éditeur
- For On-premise deployment we generally recommend setting up the API Gateway cluster inside the DMZ to run the API proxy applications and communicate to the gateway restricted to only between the API Web management console, the MMC and the service implementations themselves via another firewall and load balancer.
- This is a hybrid configuration, with the API Gateway hosted on CloudHub where the API proxy applications are deployed on CloudHub with API Gateway runtime.
- For cloud deployments, the options depend on whether VPC is part of the infrastructure. For a configuration with VPC, some CloudHub workers can be dedicated to run API proxy applications and be left outside the VPC, with the CloudHub workers that service implementations are deployed on will be inside the VPC and act like they are part of the internal network.
- For any design reason, like limit of number VPC connections or If VPC is not expected to be used, then generally API proxy applications will not be needed. The service implementation applications on CloudHub will be deployed onto API Gateway runtime.