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.

Realigning DevOps practices to support Microservices


Published on

Understand the realities of building microservices architecture applications in a large organization
Explore the cultural shifts required when teams (of any size) embark upon something as transformational as new architectural paradigms (microservices specifically)
Discover lessons Capital One learned

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Realigning DevOps practices to support Microservices

  1. 1. Realigning DevOps Practices To Support Microservices Irakli Nadareishvili, Capital One. Raji Chockaiyan, Capital One. February, 2019
  2. 2. SPOILER ALERT: What we actually care about is: increasing speed of delivery without safety and quality compromises.
  3. 3. inadarei Speed vs. Safety
  4. 4. inadarei Complex Apps = Multiple Parts, Multiple Teams Account Initiation Fraud Detection Identity Decisioning Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov 1.0 2.0 3.0 4.0 2.0 3.0 4.0 5.0 1.0 2.0 3.0 4.0 5.0 6.0 1.0 2.0 3.0 4.0 coordination coordination coordination coordination coordination coordinationcoordination
  5. 5. MICROSERVICE ARCHITECTURE (MSA) BENEFITS Benefits Include: • Technology heterogeneity • Resilience • Scaling • Ease of Deployment • Organizational Alignment • Composability • Optimizing for Replaceability -- Sam Newman Benefits TL;DR • Microservice Architecture is primarily about reducing coordination costs of aligning efforts of multiple teams/developers working on a complex system -- Irakli Nadareishvili
  6. 6. 11 Microservices Way: “Speed and Safety at Scale and in Harmony” – Need for coordination is why we constantly compromise between speed and safety.
  7. 7. inadarei 11 Reduction of batch size is the recurring theme for speed: 1. Agile – smaller batches in project management. 2. Lean – smaller batches in product management. 3. CI/CD – smaller batches in ops/deployment and QA. 4. Microservices – smaller batches of design/architecture! “Slay the monolith”: Microservices close the alignment loop! Conway’s Law: “Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure”.
  9. 9. COMPLIANCE GATES = SAFETY Source Control mechanisms Secure storage of application binary Quality checks Access Controlled Environment management Security Checks
  10. 10. STAGES OF COMPLIANCE AUTOMATION Manual Certification Semi Manual Certification Instant Certification ● 16 Stage gates ● Teams manually submit evidences ● Compliance team manually validate the evidences ● Team is certified to do automated deployment ● Consolidated stage gates ● Teams submit evidence via pipelines ● Compliance team manually validate the evidences ● Team is certified to do automated deployments ● Continuous Governance to auto- validate compliance to principles, based on the application profile
  11. 11. A GOOD PIPELINE = MAXIMIZE SPEED Reusable building blocks Flexible Orchestration Generator of Templated Pipelines
  12. 12. DECLARATIVE PIPELINES Certified Template with immutable stages Anyone who use the certified template, will automatically be certified that they are meeting the compliance gate Flexible enough to add Implementations Once we create the template, we will lock down the stages and not the implementations. Easier inner sourcing One certified template for each application category. Other teams should be able to contribute easily their own implementation. with the goal of simplicity
  13. 13. TEMPLATE EXAMPLE Above is the template from Spinnaker.
  14. 14. Choose the ImplementationChoose your Environment TWO EASY STEPS
  15. 15. RESULTING IN..
  16. 16. REALIZING THE BENEFITS OF COMPLIANT, AUTOMATED DEPLOYMENTS Average Number of deployments per month Average Number of production impacting incidents Mean time to resolve incidents +95% -90% -50%
  17. 17. Confidential
  18. 18. Rate today’s session Session page on O’Reilly Events App