The company had previously used a monolithic architecture with slow feedback and high-risk releases. They transitioned to a microservices architecture running on Docker containers 3 years ago. This provided piecewise releases, easier testing and isolation, and low-risk releases. They further improved by implementing services discovery, canary deployments, and isolating databases. More improvements like Pact testing were still needed. Overall the changes to microservices and containers helped solve their previous problems of slow feedback and high-risk releases.

1. How We Cleaned Up The
Mess
1

2. Introduction

3. 2015
The Mess

4. The History

5. 2015
Architecture Trajectory
● Age of the Monolith (5 Years Ago)
○ Monolithic UI and Backend
○ Unit and Manual Testing
○ Monthly Deployments
○ Infrastructure Monitoring

6. 2015
Architecture Trajectory
● Age of the Service-Oriented Arch. (3 Years Ago)
○ Coarse Grained Services (Tomcat)
○ Unit and Service Level Testing
○ Weekly Deployments
○ Graphite Dashboards

7. 2015
Architecture Trajectory
● Age of the Micro Architecture (1 Year Ago)
○ HTTP Microservices
○ Docker Managed
○ Unit, Functional Testing
○ On Demand Deployment
○ Application and Infrastructure Monitoring

8. What Went Wrong

9. 2015
The Mess
● High Risk Releases

10. 2015
The Mess
● Slow Feedback

11. A Warning

12. 2015

13. How We Fixed It

14. 2015
Containers
● Docker makes deployment trivial
- $ docker run myapp

15. 2015
Docker Registry
● Push and pull images from dev to prod!

16. 2015
REQUEST:
{
'id': 1,
'container': {
'image': '...',
...
},
executor: ...,
'cpus: 0.05,
'instances': 4,
'memory': 400.0
}
Build Script
Bamboo
Build
Plan
Marathon
Master
Mesos
Master
Mesos Slave
Executor
Docker
Daemon
Docker
Registry

17. 201517

18. 201518

19. 2015
Microservices
● How they solve the problem
- Piecewise releases
- Easier to understand

21. 2015
Fast Feedback
● Easier Testing
- Contracts
- Isolation
- Easy to reason about
Test
Code
Release

22. 2015
Low Risk Releases
● No downtime
● Easy rollback
● Canary Testing

23. 2015

24. 2015
Service Discovery
24

25. 2015
Atlassian
Bamboo
Cerebro
New
Relic
Canary Isolated
Microservices
Microservices
Partial Full
UIs
Thrift
Queues
DBs
Partial

26. 2015
Canary Isolated:
Contact Service

27. 2015
Canary Isolated:
Contact Service

28. 2015
Canary Isolated:
Contact Service

29. More To Do

30. 2015
More to Come
● Database isolation
● Pact

31. References

32. 2015
● http://www.stavros.io/posts/microservices-
cargo-cult/
● http://martinfowler.com/bliki/
MicroservicePrerequisites.html
● http://martinfowler.com/articles/
consumerDrivenContracts.html
● http://martinfowler.com/bliki/
MicroservicePremium.html