Microservices Adoption Workshop

For technology and project stakeholders: This workshop provides a fast-paced roadmap on which aspects of Microservices will benefit your organization, and how to adopt Microservices architecture patterns in the real-world. 

In this course, you will learn:

• How to adopt or improve your usage of microservices
• Hype vs. reality – learn where microservices work well and where they may not be appropriate
• Integration of microservices architecture patterns for greater speed, reduced risk and reduced cost
• Which recent technologies combine to make microservices practical and accessible
• How to reduce disruption to user-facing products with microservices
• Where microservices fit with related IT trends such as DevOps, Continuous Integration and Delivery, Test Automation, Security and others
• How to use microservices to tackle difficult IT challenges like legacy hardware, compute and software assets that need refactoring
• Practical steps to take to begin realizing the benefits of microservices
• How to discuss and present the business case for microservices to senior stakeholders
• The roles played by various functional members of a technology organization when leveraging microservices

Who Should Attend:
This course is for anyone involved in or impacted by the usage of microservices architecture patterns in the technology organization. You don’t have to be an engineer to benefit from this workshop, but you should have an understanding of the role IT services and software development projects integrate with your organization.

• Architects
• Developers
• Functional IT managers and leaders
• Business and systems analysts
• IT Directors
• Project and program managers
• PMO staff and business decision makers
• Agile & DevOps practitioners
• Coaches and consultants

Course Outline:

1. Intro to Microservices
A.      Optimize for speed, not efficiency
B.      Case Study: General Electric
             1)      Throughput
             2)      Waste
C.      Amazon Web Services Case Study (SOA/Microservices)
             1)      Problem: Scaling the Organization and the ‘Big ball of mud’
             2)      Conway’s Law
             3)      Service Oriented Architecture
             4)      Forced Self Service Mandate
             5)      Results
D.     Intro to Containers (encapsulation)
             1)      What is Docker
             2)      Docker concepts
             3)      Container encapsulation/ideal use cases
             4)      Benefits
             5)      VM’s vs Container use cases
             6)      Docker Architecture
             7)      Continuous integration patterns
             8)      Docker Security
E.      Microservice challenge: Continuous Integration Service
             1)      On Premise
             2)      SaaS Service             

2.      Microservices in Development
A.      Uber Case Study
            1)      2000 services, 1000 engineers
            2)      Tradeoffs             B.      Box Case Study
           1)      Traditional service deployment with bare metal
           2)      10x faster workflow with Devops practices
C.      Microservice challenge: Image repository
           1)      Docker repository development instance
           2)      On Premise Service
           3)      SaaS solution
D.     Intro to Kubernetes (Containers at Google)
           1)      Prerequisites
           2)      Containers
           3)      Container User Experience
           4)      New Container Capabilities
           5)      Gaps using Containers in Production
E.      Core Concepts
           1)      Cluster Orchestration
           2)      Open Source
           3)      Benefits
           4)      Design Principles
F.       Architecture
G.     Kubernetes Features

3.      Microservices in Production
A.      Spotify Case Study
           1)      810 Services, 477 engineers
B.      Microservice challenge: Service discovery
           1)      Skydns
           2)      Consul
C.      Security
           1)      Goals
           2)      Roles
           3)      Attribute Based Access Control
           4)      Policies
           5)      Service Accounts
           6)      Secrets
D.     Fourth Microservice challenge: Secrets
           1)      Vault
           2)      Kubernetes Secrets API

4.      Putting it all together
A.      Why Microservices?
           1)      Enabling scalability in the organization
           2)      Tradeoffs
           3)      Fault Tolerance
           4)      Throughput
           5)      Waste
B.      Discussion – what does a Microservices framework mean for your organization?
C.      How do we organize an action plan for practical implementation of Microservices?