1.
Microservices, DevOps, Continuous
Delivery – More Than Three
Buzzwords
Eberhard Wolff
Fellow
@ewolff

2.
Microservices,
DevOps, Continuous
Delivery –
How Do They Relate?

3.
Microservices,
DevOps, Continuous
Delivery –
How Do They Solve
Problems?

4.
http://microservices-buch.de/ http://microservices-book.com/

5.
Microservices?

6.
UNIX Philosophy
> Write programs that do one thing and do it
well
> Write programs to work together
> Write programs with a common interface

7.
Definition
Microservice
> Independent deployment unit
> Separate data handling & storage
> Should include UI
> Order process, Billing, Catalog…
> Process
> VM
> Docker container Server
Micro
Service

8.
Deployment Monolith
> Might be well-structured inside.
> But: Can only be deployed as a whole

9.
Continuous Delivery:
Build Pipeline
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Deploy Deploy Deploy Deploy
Automated
Reproducible
Fast

10.
Continuous Delivery:
Build Pipeline
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Deploy Deploy Deploy Deploy
Billing

11.
Continuous Delivery
Pipeline too complex
or slow?

12.
Continuous Delivery
Pipeline too complex
or slow?
Consider changing the
architecture!

13.
Microservices:
Challenges
> 50 or 100 Microservices
> Deployment?
> Monitoring?
> Log Analysis?
> Need Automation
> Need common foundation for operations
> Small deployment units are not enough

14.
Continuous Delivery
Pipeline
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Integration
Test
Microservice Complete System
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing

15.
Integration
Tests
Tests
Microservices
Unit Tests

16.
Microservices can
only be deployed
independently if tests
are independent!

17.
Microservices can
only be deployed
independently if your
Continuous Delivery
Pipeline works.

18.
Microservices +
Continuous Delivery!

19.
Why all the hassle?

20.
Conway‘s Law
Architecture
copies
communication structures
of the organization

21.
Conway’s Law as a
Limit
> Organization drives architecture
> Teams of experts
> i.e. UI, logic & database team
> Three technical artifacts

22.
E Commerce
Shop
Change
Order
Process!
UI
Logic
DB

23.
time
DB
Team Sprint
Logic
Team Sprint
GUI
Team Sprint
3 sprints

24.
Order SearchBilling
Team for each business feature
Let architecture drive the organization
Order Billing Search

25.
Deployment Monolith
+ Conway’s Law
Deployment Monolith
Stories
Technical Coordination
Coordinating Releases
StoriesStories
Order Billing Search

26.
Team can deploy without integration
Changes can be deployed independently & quickly
Strong & enforced modularization
Technology stack per Microservice
One or many Microservices per Team
Synergy Microservices / Conway’s Law
Order SearchBilling
Order Billing Search

27.
Microservices
Microservice
Stories
Technical
Coordination
Microservice
Stories
Technical
Coordination
Microservice
Stories
Technical
Coordination
Order Billing Search
Release Release Release

28.
Microservices:
Challenges
> Deployment?
> Monitoring?
> Log Analysis?
Ops

29.
Micro- and Macro-
Architecture

30.
Macro-Architecture
> Global decision
> Influence the whole system
> i.e. all Microservices
> Less Marco-Architecture – less coordination

31.
Micro-Architecture
> Local decisions
> Per Microservice

32.
Macro- and Micro-
Architecture for Ops
> Macro
> Define Log Analysis, Monitoring, Deployment tools
> Defined globally
> Micro
> Concrete deployment, monitoring, logging
> Defined per team / Microservice

33.
Microservices Teams
need many technical
skills.

34.
Microservices Teams
need Ops.

35.
DevOps

36.
DevOps /
Microservices
> Teams consist primarily of Devs
> Devs interested in Docker, ELK ...
> ... lots of experience in Ops
> More Ops effort

37.
Microservices = huge
opportunity for Ops!

38.
How Much DevOps is
Needed?
> Should all teams do full ops for their
services?
> IMHO optional
> But: Organizational barriers might cause
additional technical complexity

39.
Continuous Delivery:
Build Pipeline
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Dev Ops
Common Technologies
Log, Monitoring, Deployment

40.
DevOps =
Collaboration not
Organization

41.
This changes software
development
fundamentally.

42.
Maintainability

43.
Maintainability:
Classical Approach
> Clear architecture
> Good code quality
> Many tests
Dev

44.
Maintainability:
New Approach
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Fast und Reliable
Fast Feedback

45.
Maintainibility:
New Approach
> Continuous Delivery simplifies roll out
> ...and test them
> ...and monitor them
> Microservices limit size and risk of changes
DevOps

46.
Scalability

47.
Scalabilty:
Classical Approach
> Implement technical constraints
> E.g. statelessness
> Use appropiate technologies
Dev

48.
Performance Risk
> Hard to really predict performance
> Load test simulate user on a different
environment

49.
Scalability:
Alternative Approach
> Don‘t do anything stupid in the architecture
> Identify bottleneck
> Eliminate bottleneck
> Common technique

50.
Enable Alternative
Approach
> Monitoring to identify bottleneck
> Fast deployment to eliminate bottleneck
DevOps

51.
Maintainability: New
Approach
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Fast
Monitor all relevant data

52.
Conclusion

53.
Conclusion
> Synergy:
Microservices and Continuous Delivery
> Microservices and Continuous Delivery
support and require DevOps
> DevOps = Collaboration
> Enable alternative approaches e.g. to
maintainability and scalability

54.
Thank You!
@ewolff