Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Case Study: How to move from a Monolith to Cloud, Containers and Microservices

5,043 views

Published on

This session shows a case study about successfully moving from a very complex monolith system to a cloud-native architecture. The architecture leverages containers and Microservices to solve issues such as high efforts for extending the system, and a very slow deployment process. The old system included a few huge Java applications and a complex integration middleware deployment.

The new architecture allows flexible development, deployment and operations of business and integration services. Besides, it is vendor-agnostic so that you can leverage on-premise hardware, different public cloud infrastructures, and cloud-native PaaS platforms.

The session will describe the challenges of the existing monolith system, the step-by-step procedure to move to the new cloud-native Microservices architecture, and why containers such as Docker play a key role in this scenario.

A live demo shows how container solutions such as Docker, PaaS cloud platforms such as CloudFoundry, cluster managers such as Kubernetes or Mesos, and different programming languages are used to implement, deploy and scale cloud-native Microservices in a vendor-agnostic way.

Key takeaways for the audience:
- Best practices for moving to a cloud-native architecture
- How to leverage microservices and containers for flexible development, deployment and operations
- How to solve challenges in real world projects
- Understand key technologies, which are recommended
- How to stay vendor-agnostic
- See a live demo of how cloud-native applications respectively services differ from monolith applications regarding development and runtime

Published in: Technology
  • Be the first to comment

Case Study: How to move from a Monolith to Cloud, Containers and Microservices

  1. 1. Kai Wähner Technology Evangelist kontakt@kai-waehner.de LinkedIn @KaiWaehner www.kai-waehner.de TIBCO Meetup Mumbai, India (February 2017) Case Study: How to move from a Monolith to Cloud, Containers and Microservices
  2. 2. © Copyright 2000-2017 TIBCO Software Inc. Evolving Demands from the Business AGILITY & SPEED REDUCED CYCLE TIMES WEB SCALE LOWER COST FAIL FAST
  3. 3. © Copyright 2000-2017 TIBCO Software Inc. • A cloud-native architecture enables flexible and agile development • Only vendor- and platform-agnostic architectures are future-safe • Various programming languages, open source frameworks and middleware complement each other well in a Microservices world Key Takeaways
  4. 4. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  5. 5. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  6. 6. © Copyright 2000-2017 TIBCO Software Inc. Big and Complex Monolith Monolith 1 „Big SOA Application“ (Middleware + Java) Monolith 2 Monolith 3 CRM ERM Host ... Virtual Machine(s) Cloud-Ready On Premise Public Cloud
  7. 7. © Copyright 2000-2017 TIBCO Software Inc. #1 On premise will not die. Not everything will or should go to the cloud!
  8. 8. © Copyright 2000-2017 TIBCO Software Inc. Various Technologies Glued Together Middleware
  9. 9. © Copyright 2000-2017 TIBCO Software Inc. Development Environment Zero Coding Code Everything or anything in between
  10. 10. © Copyright 2000-2017 TIBCO Software Inc. #2 Visual coding works, even for very complex scenarios. It can be combined with coding, too!
  11. 11. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  12. 12. © Copyright 2000-2017 TIBCO Software Inc. 12 Microservices Example http://www.ibm.com/developerworks/cloud/library/cl-bluemix-microservices-in-action-part-1-trs/ Each tile is a microservice “bookflights” interacts with other microservices Height corresponds to usage Each microservice can be Independently managed à Shorter time to results and increased flexibility / scalability à Replace small pieces instead of a complete application
  13. 13. © Copyright 2000-2017 TIBCO Software Inc. From a Monolith to Microservices Business Service A1 Java Cloud-Ready On Premise Public Cloud CRM ERM Host ... Business Service A2 Python Integration Service A3 Middleware Business Service B1 Java Business Service B3 Python Business Service B2 Go Integration Service B4 Middleware Virtual Machine(s)
  14. 14. © Copyright 2000-2017 TIBCO Software Inc. Various Forms of (Micro)Services Integration Service Monolith application SOA Integration Service Service ServiceService Service SaaS Service BPM Service
  15. 15. © Copyright 2000-2017 TIBCO Software Inc. Distributed Microservice Architecture http://blogs.gartner.com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/ ”That complexity has moved and […] increased [to] the outer architecture.”
  16. 16. © Copyright 2000-2017 TIBCO Software Inc. New Challenges Emerging… http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html ”[…] when considering Microservice like architectures, it's really important to not be attracted to the hype on this one as the challenges and costs are as real as the benefits." • Different Languages / Technologies • DevOps Skills Required • Distributed System Complexity • Distributed Configuration • Service Discovery • Resiliency • Client Side Load Balancing • Testability Challenges • Orchestration / Integration • Spaghetti Communication (again ?!) • Re-Delivery • Re-Route • Cache • ...
  17. 17. © Copyright 2000-2017 TIBCO Software Inc. New Design Patterns Emerging… Resilience Design Patterns Features • Fail fast and rapidly recover • Prevent cascading failures • Latency tolerance logic • Fault tolerance logic • Fallback Options http://martinfowler.com/bliki/CircuitBreaker.html https://github.com/Netflix/Hystrix/wiki maxFailures = 5 resetTimeout = 1min callTimeout = 10s à maxFailures++ Example: Circuit Breaker
  18. 18. © Copyright 2000-2017 TIBCO Software Inc. #3 Microservices are not free lunch. They do not fit into every scenario!
  19. 19. © Copyright 2000-2017 TIBCO Software Inc. Open API and API Management
  20. 20. © Copyright 2000-2017 TIBCO Software Inc. New Design Patterns Emerging… http://samnewman.io/patterns/architectural/bff https://www.thoughtworks.com/insights/blog/bff-soundcloud Example: Backends for Fronteds (BfF) ?
  21. 21. A P I M A N A G E M E N T © Copyright 2000-2017 TIBCO Software Inc. From Microservices to Open APIs Business Service A1 Java Cloud-Ready On Premise Public Cloud CRM ERM Host ... Business Service A2 Python Integration Service A3 Middleware Business Service B1 Java Business Service B3 Python Business Service B2 Go Integration Service B4 Middleware API API Virtual Machine(s)
  22. 22. © Copyright 2000-2017 TIBCO Software Inc. #4 Design Microservices with open APIs in mind!
  23. 23. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  24. 24. © Copyright 2000-2017 TIBCO Software Inc. “Cloud washing is the purposeful and sometimes deceptive attempt by a vendor to rebrand an old product or service by associating the buzzword ‘cloud’ with it [and offering it via a public cloud infrastructure].” Cloud Washing vs. Cloud Native http://searchcloudstorage.techtarget.com/definition/cloud-washing !
  25. 25. © Copyright 2000-2017 TIBCO Software Inc. 12 (or 13, 14, …) Factor Apps for Cloud Native Microservices Codebase One codebase tracked in revision control, many deploys. Dependencies Explicitly declare and isolate dependencies. Config Store config in the environment. Backing Services Treat backing services as attached resources. Build, Release, Run Strictly separate build and run stages. Processes Execute the app as one or more stateless processes. Port Binding Export services via port binding. Concurrency Scale out via the process model. Disposability Maximize robustness with fast startup and graceful shutdown. Dev / Prod Parity Keep dev, staging, and prod as similar as possible. Logs Treat logs as event streams. Admin Processes Run admin/mgmt tasks as one-off processes. https://12factor.net/
  26. 26. © Copyright 2000-2017 TIBCO Software Inc. • Scalable services • Service Discovery • Load balancing and failover • Resiliency • DevOps and automation • Usage of public cloud platforms, but also private or hybrid • Self-service, pay-as-you-use, multi-tenancy • Vendor-agnostic deployment Cloud Native (à not just Microservices) à Focus on business problems
  27. 27. © Copyright 2000-2017 TIBCO Software Inc. #5 Cloud-Native means much more than a “cloud-washed” application deployed to a cloud provider!
  28. 28. © Copyright 2000-2017 TIBCO Software Inc. == The Momentum of Containers How to deploy independent Applications or (Micro)Services? Garden
  29. 29. © Copyright 2000-2017 TIBCO Software Inc. Why Containers? http://www.slideshare.net/andersjanmyr/docker-the-future-of-devops Containers enable: • Lightweight deployment • Automation • Better resource utilization • Scaling up and down quickly • Platform agnostic deployment • Innovation and Fail Fast Concepts • Standardization ? Ø The Open Container Initiative (OCI) Ø Docker Fork Discussions (!!!)
  30. 30. A P I M A N A G E M E N T © Copyright 2000-2017 TIBCO Software Inc. From Microservices and Open APIs to Containers Business Service A1 Java CRM ERM Host ... Business Service A2 Python Integration Service A3 Middleware Business Service B1 Java Business Service B3 Python Business Service B2 Go Integration Service B4 Middleware API API Cloud-Ready On Premise Public Cloud Container(s) Container(s) Container(s)
  31. 31. © Copyright 2000-2017 TIBCO Software Inc. #6 Microservices and Containers are often used together, but also work very well without each other!
  32. 32. © Copyright 2000-2017 TIBCO Software Inc. Cloud-Native Architecture Containers are just the Foundation for a Cloud Native Architecture!
  33. 33. © Copyright 2000-2017 TIBCO Software Inc. Cloud Native Landscape (created by CNCF) https://github.com/cncf/landscape
  34. 34. Cloud Native Platform (Infrastructure-as-a-Service) Choose your IaaS Private or Hybrid Cloud Reduced costs of Infra Self-hosted & Controlled Env Servers Storage Network IaaS
  35. 35. Cloud Native Platform (Platform-as-a-Service) Choose your PaaS / Container Cloud-Native App Dev Self-service agile infrastructure Elasticity & Scalability OS & Containers Scalability Routing Logging / Monitoring PaaS
  36. 36. © Copyright 2000-2017 TIBCO Software Inc. Cloud Native Platform (IaaS + PaaS) Choose your IaaS Choose your PaaS / Container Private or Hybrid Cloud Cloud-Native App Dev Reduced costs of Infra Self-service agile infrastructure Self-hosted & Controlled Env Elasticity & Scalability Servers Storage Network OS & Containers Scalability Routing Logging / Monitoring PaaS IaaS
  37. 37. © Copyright 2000-2017 TIBCO Software Inc. Kubernetes (K8S) http://kubernetes.io/docs/getting-started-guides/#cloud
  38. 38. © Copyright 2000-2017 TIBCO Software Inc. Cloud Foundry http://www.slideshare.net/cdavisafc/cloud-foundry-technical-overview
  39. 39. © Copyright 2000-2017 TIBCO Software Inc. Apache Mesos – a “Cloud Operating System” http://www.slideshare.net/Docker/building-web-scale-apps-with-docker-and-mesos/30 • Enterprises have to manage different clusters with different technologies • Based on containers (but no specific technology, e.g. you can use Docker and rkt)
  40. 40. © Copyright 2000-2017 TIBCO Software Inc. “The basic resource for CaaS is a container, rather than a virtual machine (VM) or a bare metal hardware host system.” Container-as-a-Service (CaaS) http://searchcloudcomputing.techtarget.com/definition/Containers-as-a-Service-CaaS
  41. 41. © Copyright 2000-2017 TIBCO Software Inc. Serverless Computing • Bring a function (not an entire application) up for one single request. • No cluster or server instance management. • Small microservice-style functions running for a few (milli)seconds or at latest a few minutes. • 100% utilization (!!!) “Sponsored by Red Hat / JBoss"
  42. 42. © Copyright 2000-2017 TIBCO Software Inc. #7 Be cloud platform agnostic. The (container) world changes fast!
  43. 43. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  44. 44. A P I M A N A G E M E N T © Copyright 2000-2017 TIBCO Software Inc. From Containers to a Cloud-Native Platform Business Service A1 Java CRM ERM Host ... Business Service A2 Python Integration Service A3 Middleware Business Service B1 Java Business Service B3 Python Business Service B2 Go Integration Service B4 Middleware API API Cloud-Native On Premise Public Cloud Container(s) Container(s) Container(s) Cloud-Native Platform
  45. 45. © Copyright 2000-2017 TIBCO Software Inc. #8 Containers are a lower level technology. Only the infrastructure provider should care, but not the application developer!
  46. 46. © Copyright 2000-2017 TIBCO Software Inc. DevOps Elements – Culture and Technology! Process Tools Automation Culture Continuous Integration/ Continuous Development APIs MicroservicesFrequent releases Collaboration
  47. 47. © Copyright 2000-2017 TIBCO Software Inc. #9 Automation (CI / CD / DevOps) and the related cultural change are key for success. Especially for Cloud-Native Microservices!
  48. 48. © Copyright 2000-2017 TIBCO Software Inc. Microservices, Cloud, Container, PaaS, APIs, Coding, Visual Dev, … Show me some cloud native examples!
  49. 49. © Copyright 2000-2017 TIBCO Software Inc. • Open Source • Runs on OpenShift PaaS (which is based on Kubernetes) • Also available as iPaaS • JBoss Fuse (based on Apache Camel and JBoss A-MQ) • For Integration Specialists • Focus on writing source code JBoss Middleware Services https://www.openshift.com/container-platform/middleware-services.html
  50. 50. © Copyright 2000-2017 TIBCO Software Inc. JBoss Example: Apache Camel Integration Service Java DSL new RouteBuilder() { public void configure() { from(”jms:myQueue").loadBalance() .circuitBreaker(2, 1000L, MyCustomException.class) .to("mock:result"); }}; XML DSL <route> <from uri=“jms:myQueue"/> <loadBalance> <circuitBreaker threshold="2" halfOpenAfter="1000"> <exception>MyCustomException</exception> </circuitBreaker> <to uri="mock:result"/> </loadBalance> </route>
  51. 51. © Copyright 2000-2017 TIBCO Software Inc. WSO2 http://wso2.com/cloud/paas/ • Open Source • Runs on different cloud platforms • Also available as iPaaS • WSO2 Products (like ESB or CEP) containerized for cloud offerings • WSO2 Microservices Framework for Java • For Integration Specialists • Focus on writing source code and configuration
  52. 52. © Copyright 2000-2017 TIBCO Software Inc. TIBCO • Runs on various cloud platforms (TIBCO BusinessWorks Container Edition) • Native integration with 3rd party frameworks like Consul or Hystrix • Also available as iPaaS (TIBCO Cloud Integration) • Focus on visual coding and productivity • Powerful IDE (Visual Coding) + Web user interface • For Integration Specialists and Citizen Integrators
  53. 53. © Copyright 2000-2017 TIBCO Software Inc. #10 A cloud native architecture leverages various programming languages, open source frameworks and middleware!
  54. 54. © Copyright 2000-2017 TIBCO Software Inc. 1) A Legacy Monolith Application 2) The Move to Microservices 3) The Need for a Cloud Native Platform 4) Cloud Native Microservices 5) Live Demo with Docker, Kubernetes, Cloud Foundry Agenda
  55. 55. © Copyright 2000-2016 TIBCO Software Inc. Develop Deploy Commit Build Config Demo Setup
  56. 56. © Copyright 2000-2017 TIBCO Software Inc. Live Demo Cloud-Native Middleware Development with • Pivotal Cloud Foundry • Spring Cloud Config • Docker • Kubernetes • Consul • Hystrix • TIBCO BusinessWorks Container Edition • TIBCO Mashery • Papertrail
  57. 57. © Copyright 2000-2017 TIBCO Software Inc. • A cloud-native architecture enables flexible and agile development • Only vendor- and platform-agnostic architectures are future-safe • Various languages, open source frameworks and middleware complement each other Key Takeaways
  58. 58. Questions? Please contact me! Kai Wähner Technology Evangelist kontakt@kai-waehner.de @KaiWaehner www.kai-waehner.de LinkedIn

×