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.

Made for Each Other: Microservices + PaaS

3,270 views

Published on

Companies need to build better software faster to compete. But existing monolithic applications, legacy platforms, and lengthy operational deployment cycles are holding innovation back. Microservices are becoming the cloud architecture of choice because they offer the ability to loosely couple applications into discrete services that can be surgically changed without requiring disruptive overhauls. This approach enables the responsiveness and rapid change needed by the business.

Enterprise PaaS is a critical foundation to simplify the operations, governance, and health management of these new architectures. Together with a DevOps culture, microservices and PaaS are the engine that drives innovation at speed.

Published in: Technology

Made for Each Other: Microservices + PaaS

  1. 1. DevOps, ! microservices,! & the new ! composable enterprise Donnie Berkholz! @dberkholz
  2. 2. What in the world ! is DevOps, anyhow?
  3. 3. Agile, truly tip to tail Business to customer
  4. 4. Tear down all the silos Flickr: kalandrakas
  5. 5. “Infrastructure as code”
  6. 6. #monitoringsucks/#monitoringlove
  7. 7. Organizations with high performing DevOps organizations were 2x more likely to exceed profitability, market share and productivity goals…! !!!! …and had 50% higher market capitalization growth over 3 years… Source: Puppet Labs 2014 State Of DevOps Gene Kim
  8. 8. Who Is Doing DevOps? § Google, Amazon, Netflix, Etsy, Spotify, Twitter, Facebook … § CSC, IBM, CA, SAP, HP, Microsoft, Red Hat … § GE Capital, Nationwide, BNP Paribas, BNY Mellon, ! World Bank, Paychex, Intuit … § The Gap, Nordstrom, Macy’s, Williams-Sonoma, Target … § General Motors, Northrop Grumman, LEGO, Bosche … § UK Government, US Department of Homeland Security … § Kansas State University… Who else? Gene Kim
  9. 9. CI/CD & the ! changing roles ! of Devs and Ops
  10. 10. Test your infrastructure like your code
  11. 11. The composable enterprise! and the Yegge memo
  12. 12. Containerization
  13. 13. Stack Overflow container traction
  14. 14. Microservices (not monoliths) Separation of (business) concerns into services accessed via REST APIs Resilient to failure, easily reusable, etc
  15. 15. Platform as a Service (PaaS) Has its time finally arrived?
  16. 16. The view from 40,000 feet continuousautomation.com
  17. 17. Minimizing risk, Maximizing agility l Architecture: Microservices, monitoring l Code: Continuous integration, feature flags l Servers: Continuous delivery, infrastructure as code l Services: Rolling updates, resilient engineering l Product: Continuous deployment, restricted audience
  18. 18. Donnie Berkholz dberkholz@redmonk.com Twitter/IRC: dberkholz
  19. 19. Made for Each Other: Microservices + PaaS How Pivotal CF and Spring Cloud Enable Architectural Innovation Matt Stine (@mstine) Platform Engineer © 2014 Pivotal Software, Inc. All rights reserved. ‹#›
  20. 20. Continuous Delivery Physical/Virtual Pivotal CF Infrastructure Applications Monoliths Microservices DevOps Feedback Rapid Iteration Horizontal Scale Diversity of Clients © 2014 Pivotal Software, Inc. All rights reserved. 21
  21. 21. New Architectural Constraints • Pivotal CF optimizes for 12 Factor Linux applications © 2014 Pivotal Software, Inc. All rights reserved. 22
  22. 22. Twelve Factors • One Codebase/Many Deploys • Explicit Isolated Dependencies • Config via Environment • Attached Backing Services • Separate Build/Release/Run • Stateless Processes • Export Services via Port Bindings • Scale Out via Processes • Disposable Instances • Dev/Prod Parity • Logs == Event Streams • Admin Tasks == Processes © 2014 Pivotal Software, Inc. All rights reserved. 23
  23. 23. New Architectural Constraints • Pivotal CF optimizes for 12 Factor Linux applications • Microservices: a radical departure from traditional monolithic applications • In both cases, the enterprise is forced to “think different.” © 2014 Pivotal Software, Inc. All rights reserved. 24
  24. 24. How XP Practices Support Each Other http://www.kusmin.eu/wiki/index.php/How_XP_Practices_Support_Each_Other © 2014 Pivotal Software, Inc. All rights reserved. 25
  25. 25. A Mutualistic Symbiotic Relationship… Microservices Pivotal CF http://en.wikipedia.org/wiki/Symbiosis#Mutualism © 2014 Pivotal Software, Inc. All rights reserved. 26
  26. 26. http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html © 2014 Pivotal Software, Inc. All rights reserved. 27
  27. 27. Paying for your lunch… • Significant Operations Overhead • Substantial DevOps Skills Required • Implicit Interfaces • Duplication of Effort • Distributed System Complexity • Asynchronicity is Difficult! • Testability Challenges © 2014 Pivotal Software, Inc. All rights reserved. 28
  28. 28. You must be this tall to use Microservices… • RAPID PROVISIONING • BASIC MONITORING • RAPID APPLICATION DEPLOYMENT • DEVOPS CULTURE https://www.flickr.com/photos/gusset/3723961589 http://martinfowler.com/bliki/MicroservicePrerequisites.html © 2014 Pivotal Software, Inc. All rights reserved. 29
  29. 29. It’s gonna take a platform… Pivotal CF Spring Cloud © 2014 Pivotal Software, Inc. All rights reserved. 30
  30. 30. Platform Features • Environment Provisioning • On-Demand/Automatic Scaling • Failover/Resilience • Routing/Load Balancing • Data Service Operations • Monitoring • Distributed/Versioned Config • Service Registration/Discovery • Routing/Load Balancing • Service Integration • Fault Tolerance • Asynchronous Messaging © 2014 Pivotal Software, Inc. All rights reserved. 31
  31. 31. http://projects.spring.io/spring-cloud © 2014 Pivotal Software, Inc. All rights reserved. 32
  32. 32. • Eureka • Hystrix + Turbine • Ribbon • Feign • Zuul • Archaius + http://netflix.github.io © 2014 Pivotal Software, Inc. All rights reserved. 33
  33. 33. Pivotal CF + Spring Cloud + Netflix OSS! Live Demo https://www.youtube.com/watch?v=vm8PcbcsYxU#t=2787 © 2014 Pivotal Software, Inc. All rights reserved. 34
  34. 34. Supporting Rapid Change Microservices is the first architectural style developed: Δ POST & POST DevOps Continuous Delivery © 2014 Pivotal Software, Inc. All rights reserved. 35
  35. 35. Architecture is abstract until it is operationalized. Neal Ford © 2014 Pivotal Software, Inc. All rights reserved. 36
  36. 36. Architectures that aren’t operationalized exist only on whiteboards. Matt Stine © 2014 Pivotal Software, Inc. All rights reserved. 37
  37. 37. OPERATIONALIZED ARCHITECTURE Microservices Pivotal CF Spring Cloud © 2014 Pivotal Software, Inc. All rights reserved. 38
  38. 38. Thank you! • @dberkholz • "The interface from Dev to Ops isn’t going away; it’s rotating” bit.ly/devops-rotating • "The parallel universes of DevOps and cloud developers” bit.ly/devops-parallel Cloud Foundry twitter.com/cloudfoundry youtube.com/user/CloudFoundry Spring twitter.com/springcentral spring.io/video • "DevOps and cloud: A view from outside the Bay Area bubble" bit.ly/devops-bubble © 2014 Pivotal Software, Inc. All rights reserved. 39
  39. 39. © 2014 Pivotal Software, Inc. All rights reserved. 40

×