Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Migration from Legacy to Microservices on Containers
Ähnlich wie Migration from Legacy to Microservices on Containers (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Migration from Legacy to Microservices on Containers
- 1. Prasad Rao prrao@AviNetworks.com Migration from Legacy to Microservices on Containers - Load Balancer / Application Delivery Controller
- 2. Agenda Application Evolution – Legacy to Microservices Application Delivery Controller - Evolution Example – photo.com Microservices Service Discovery Load Balancing Elastic Load Balancing
- 3. Application Evolution – from Monolith to Microservices Rapid Move to Distributed Application Architectures Users Discover Scale Monitor Secure Web Application Order Mgmt Customer Service Product Order Customer UI Storefront Catalog Service Catalog UI Checkout UI Order Mgmt UI Account Mgmt UI Catalog Service Review Service Login Service Order Service Customer Service Web App UI Users Firewall DNS/IPAM Load Balancer NPM/ APM App Architecture Evolution Microservices Containers Discover Scale Monitor Secure Discover Scale Monitor Secure East-West Services North-South Traffic “Loosely coupled service oriented architecture with bounded contexts” – Adrian Cockcroft
- 4. Internet Load Balancer / Application Delivery Controller (ADC) – Legacy Clients Load Balancers http://photos.com DNS A-record 12.168.59.48 12.168.59.48:80 Application Servers 10.10.37.21:80 10.10.37.24:80 10.10.45.101:111 10.10.45.102:111 10.10.45.103:111 10.10.37.22:80 10.10.37.23:80
- 5. PUBLIC CLOUD PRIVATE CLOUD (VMware, OpenStack…) SDN (Cisco ACI/...) RESTAPI Appliance SoftwareController Management • Scalable Network Services Separated control and data plane • Centralized Management Manage a single fabric, not many devices • Visibility & Analytics Actionable insights key to automation • Hybrid Cloud Single solution, any environment Application Delivery (ADC) Evolution – Appliance to Distributed Distributed Architecture with Central Control ContainerBare Metal Virtualized Public Cloud Service Engine Data Plane VM VM VM VM VM SoftwareService Engine Data Plane Software
- 6. • Controller Integration with Mesos/Docker • Add Service Engine (Service Proxies) to ALL nodes • Controller Integration with Marathon/UCP • When a new application is added, automatically create a proxy service on all Mesos nodes • Automated, non-disruptive configuration updates • Apply load balancing, auto-scaling, monitoring and security policies from central controller • Ongoing/Run-Time • Add/remove SEs to/from Mesos/Docker nodes • Auto-scale application instances using Marathon/UCP LB – Container Clustering Integration Fully Automated, Policy –Driven Deployment of Apps / Services Marathon Mesosphere Mesos Nodes Universal Control Plane
- 7. Photo.com Checkout Black List Catalog Marketing Shopping Cart Example Application – photo.com - Microservices
- 8. Photo.com Checkout Black List Catalog Marketing Shopping Cart Example Application – Microservice instances
- 9. 24 Core 256 GB Ram 4TB HD 24 Core 256 GB Ram 4TB HD 24 Core 256 GB Ram 4TB HD 24 Core 256 GB Ram 4TB HD 24 Core 256 GB Ram 4TB HD 24 Core 256 GB Ram 4TB HD UCP Nodes Universal Control Plane UCP Controller and Nodes
- 10. Photo.com .. { .YML } Universal Control Plane
- 11. Photo.com .. { .YML } Black List ….. Universal Control Plane
- 12. Photo.com .. { .YML} Black List ….. Catalog …..... Universal Control Plane
- 13. Photo.com .. { .YML} Black List ….. Catalog …..... Checkout ….. Universal Control Plane
- 14. Photo.com .. { .YML} Black List ….. Catalog …..... Checkout ….. Marketing …....... Universal Control Plane
- 15. Photo.com .. { .YML} Black List ….. Catalog …..... Checkout ….. Marketing …....... Shopping Cart ….. Universal Control Plane
- 17. Photo.com .. Black List ….. Catalog …..... Marketing …....... Shopping Cart ….. Checkout …..Universal Control Plane Service Engine Application Delivery Controller Deployment App-Evolution -> UCP -> ADC-Evolution -> UCP+ADC -> Example -> u-Svcs -> Svc-Discovery -> LB -> ELB
- 18. Photo.com Checkout Black List Catalog Marketing Shopping Cart 10.10.10.1:34519 10.10.10.2:38911 10.10.10.2:30132 10.10.10.2:43498 10.10.10.3:56721 10.10.10.5:35097 10.10.10.5:37002 10.10.10.6:57250 10.10.10.6:42703 10.10.10.1:37520 10.10.10.2:32941 10.10.10.2:39942 10.10.10.2:41498 10.10.10.3:59921 10.10.10.5:34097 10.10.10.5:30002 10.10.10.6:50250 10.10.10.6:41703 10.10.10.1:38110 10.10.10.2:31521 10.10.10.2:30942 10.10.10.2:42498 10.10.10.3:58921 10.10.10.4:39097 10.10.10.4:32002 10.10.10.6:51250 10.10.10.6:48703 10.10.10.1:58921 10.10.10.1:39097 10.10.10.2:32002 10.10.10.5:51250 10.10.10.6:48703 10.10.10.2:41498 10.10.10.3:59921 10.10.10.4:34097 10.10.10.4:30002 10.10.10.6:50250 10.10.10.6:41703 10.10.10.1:41110 10.10.10.1:56521 10.10.10.1:40942 10.10.10.2:42498 10.10.10.2:58921 10.10.10.2:39097 10.10.10.4:32002 10.10.10.4:51250 10.10.10.6:48703 VIP 172.16.0.1:10001 (Internal) VIP 172.16.0.1:10005 (Internal) VIP 172.16.0.1:10004 (Internal) VIP 172.16.0.1:10002 (Internal) VIP 172.16.0.1:10003 (Internal) VIP 12.168.59.48:80 (Public)
- 19. Photo.com .. Black List ….. Catalog …..... Marketing …....... Shopping Cart ….. Corp DNS Checkout ….. What port is checkout.avi.xyz.com? Universal Control Plane Service Engine Service Discovery
- 20. Photo.com .. Black List ….. Catalog …..... Marketing …....... Shopping Cart ….. Corp DNS Checkout ….. ADC Controller is authoritative for avi.xyz.com Universal Control Plane Service Engine
- 21. Photo.com .. Black List ….. Catalog …..... Marketing …....... Shopping Cart ….. 172.16.0.1:10001 Corp DNS Checkout ….. What port is checkout.avi.xyz.com? Universal Control Plane Service Engine
- 22. Photo.com .. Black List ….. Catalog …..... Marketing …....... Shopping Cart ….. 172.16.0.1:10001 Corp DNS Checkout ….. checkout.avi.xyz.com is 172.16.0.1:10001 Universal Control Plane Service Engine
- 23. Photo.com .. Black List ….. Catalog …..... Checkout ….. Marketing …....... Shopping Cart ….. Service EngineUniversal Control Plane Load Balancing
- 24. Photo.com .. Black List ….. Catalog …..... Checkout ….. Marketing …....... Shopping Cart ….. 10.10.10.2:41498 10.10.10.3:59921 10.10.10.3:34097 10.10.10.4:30002 10.10.10.5:50250 10.10.10.6:41703 Virtual Service 172.16.0.1:10001 Universal Control Plane Service Engine Load Balancing Checkout
- 25. Photo.com .. Black List ….. Catalog …..... Checkout ….. Marketing …....... Shopping Cart ….. 10.10.10.2:41498 10.10.10.3:59921 10.10.10.3:34097 10.10.10.4:30002 10.10.10.5:50250 10.10.10.6:41703 Virtual Service 172.16.0.1:10001 10.10.10.1:57878 10.10.10.3:41173 10.10.10.4:34097 10.10.10.4:41882 10.10.10.4:31126 10.10.10.5:41703 Virtual Service 172.16.0.1:10001 Universal Control Plane Service Engine Elastic Load Balancing – Configuration Update Checkout
- 26. Cloud Key takeaways – To Scalability Web Application Order Mgmt Customer Service Product Order Customer UI Storefront Catalog Service Catalog UI Checkout UI Order Mgmt UI Account Mgmt UI Catalog Service Review Service Login Service Order Service Customer Service Web App UI Move Application to Cloud Rearchitect Application to use Micro-Services Scale each Micro-Service on demand Use a scalable load-balancerPhoto.com Checkout Catalog Marketing ShoppingCart
- 27. Prasad Rao prrao@AviNetworks.com Thank You! Avi Networks (India) Pvt Ltd. JB House, 110, 4th Cross, 5th Block, Koramangala Industrial Layout, Bangalore 560 095, Karnataka.
Hinweis der Redaktion
- Show of hands – how many of you know what’s a load balancer, firewall, IPAM, NPM/APM?
- Show of hands – how many of you know what’s a load balancer, firewall, IPAM, NPM/APM?
- You transition your monolithic app and embrace a micro service architecture.
- But how do all these containers discover and talk to each other?
- An orchestrator and scheduler is needed to help microservices scale, such as Mesos and Marathon.
- Your developers deploy microservices directly to Marathon. Mesos decides where resources are available for your containers. Avi specific Labels embedded in the YML file of the applications – COM.AVINETWORKS.AVI_PROXY {“virtualservice”:”ip_address”:{“type”:”v4”, “addr”:”x.x.x.x”}, “analytics_policy”:{“client_insights”: “NO_INSIGHTS”,
- Containers spin up with a random port so how do your microservices talk to each other?
- Containers spin up with a random port so how do your microservices talk to each other?
- Avi Controller listens to Mesos and Marathon’s messaging bus, so when new containers are deployed, Avi Controller learns which containers belong to which microservice and also which port each container is listening on.
- When the photo.com app wants to talk to the checkout app, it connects to the VS on the Avi SE on the same node, and it load balances the traffic to the appropriate checkout containers in the cluster. Photo.com learns of the VS address from Avi’s service discovery.
- When containers move around and spin up on new ports, backend pool mapping is updated automatically.
- Unbox your application from appliance to Cloud Rearchitect to make use of micro-services So each service can scale up/down on need basis Use service-discovery along with a good load-balancer to distribute traffic across micro-services