Sam Newman: Building Microservices
Why should you attend?
Because it is focused on outcomes. We explore the pitfalls and downsides of implementing the architecture, as well as how to mitigate problems. For example: how to effectively deal with distributed transactions and the implications of CAP theorem.
You will discover whether microservices are right for you, as microservices are not a universal solution to all problems. Then you are given concrete tools to implement the migration to a microservices based architecture in an incremental fashion, all while continuing to ship new features.
Ultimately, you will walk away knowing whether microservices are the right choice for your business, and if they are, then you will have a clear idea of how to make it happen.
Who is the Masterclass for?
People who are in the process of moving to microservices, or are already on the path should get a lot out of the event. It's primarily aimed at people in technical leadership positions like tech leads and architects, but should be of use to any developer or operations person interested in how to move to microservices. Prior knowledge of service oriented architectures generally or microservices specifically is useful, but by no means essential.
This Masterclass will cover:
- What makes a good microservice.
- How to use concepts from domain driven design to define service boundaries.
- Explore how to plan and manage a migration from a monolith to the microservice architecture.
- Understand how technical choices can impact the architecture itself.
- How to manage change and governance in a microservice environment.
Sam Newman @ GOTO Academy (2019)
Agenda: Day 1
- Introducing Microservices
- What microservices are: Technology & SOA
- Advantages of microservices
- Disadvantages of microservices
- When should you use them, and when shouldn’t you use them?
- Service Modelling
- Characteristics of “good” services
- Introduction to domain driven design
- Usefulness of Bounded Contexts when defining service boundaries Splitting Out Services
- Working out where to start
- Splitting stateless services
- Database refactoring patterns
- Use of strangler and branch by abstraction patterns
- Discussion of CAP theory
- Distributed transactions
- Eventual consistency
Agenda: Day 2
- Service Collaboration
- Pitfalls of service collaboration
- Synchronous vs asynchronous
- Event-based collaboration vs Request/Response
- Coverage of technology options including: HTTP over REST & RPC; Actor frameworks; Message Brokers including Kafka
- Choreography vs Orchestration
- Testing
- End-to-end testing in a microservice world
- Test types and feedback
- Consumer-driven contracts
- Testing in production?
- Observability
- Log aggregation
- Correlation IDs
- Metrics collection
- Semantic monitoring
- Real-user monitoring
- Synthetic Transactions
- Resiliency & Scaling
- Types of scaling (scaling cube + more)
- Scaling for load vs scaling for resiliency
- Circuit Breakers and connection pooling
- Bulkheads & timeouts
- Service Meshes & Message Brokers
- User Interfaces / Mobile
- UI aggregation models
- General-purpose API gateways
- Backends-for-frontends
- GraphQL
Agenda: Day 3
- Evolutionary Architecture
- The challenges of big-bang rewrite
- How the role of the architect changes in a microservice team
- What is evolutionary architecture?
- Organisational Aspects
- Conway's Law
- Service ownership models
- Security
- Simple model for AppSec
- Threat modeling
- Standard prevention mechanisms
- Protection of data in transit
- Authentication & authorisation
- Recovering from security incidents
- Build & Deployment
- Build/CI basics
- Microservices & repo/CI mapping
- Pipeline design
- Deployment mechanisms
- Containerisation vs virtualisation
- Deployment platforms (Kubernetes et al)
- Serverless and Microservices
- Where does serverless come in?
- How does FAAS map to microservices?
- Challenges in serverless adoption
*Please note that the outlines above are purely indicative. There's the flexibility to spend more (or less) time on specific subjects, and this can usually be accommodated as the material is broken down into modules that can be swapped around. This will be determined during the class based on the direction trainee's wish to cover.