Microservices
Architectures
Hooklift, Inc.
Camilo Aguilar - Founder at Hooklift, Inc.
@c4milo at Twitter and Github
Slide 2
Slide 2 text
– Adrian Cockcroft, Netflix, Inc.
“It is a service-oriented architecture
composed of loosely coupled elements that
have bounded contexts.”
What is it?
Hooklift, Inc.
Slide 3
Slide 3 text
Hooklift, Inc.
Image Source: http://martinfowler.com/bliki/BoundedContext.html
What is it?
Slide 4
Slide 4 text
Monolithic
Image source: http://www.infoq.com/presentations/migration-cloud-microservices Hooklift, Inc.
Slide 5
Slide 5 text
Hooklift, Inc.
Image source: http://www.infoq.com/presentations/migration-cloud-microservices
Microservices
Slide 6
Slide 6 text
Hooklift, Inc.
Microservices benefits
business and developers
Slide 7
Slide 7 text
Deployments per day
• Flickr: 10
• Etsy: 50
• Netflix: 100
• HubSpot: 300
• Twitter: 7200
• Amazon: 7800
Hooklift, Inc.
Reasoning: The smaller the change the lower the risk
Also: Continuous delivery of business value
Slide 8
Slide 8 text
However, there are
also new challenges
Hooklift, Inc.
Slide 9
Slide 9 text
Hooklift, Inc.
Wheel of Doom
Slide 10
Slide 10 text
Hooklift, Inc.
Image source: http://www.infoq.com/presentations/migration-cloud-microservices
Slide 11
Slide 11 text
Hooklift, Inc.
Slide 12
Slide 12 text
If you don’t have a plan
you will choke yourself out
Hooklift, Inc.
Slide 13
Slide 13 text
How do we get there?
Hooklift, Inc.
Slide 14
Slide 14 text
Ideally, organically
Hooklift, Inc.
Slide 15
Slide 15 text
Do not force it
Hooklift, Inc.
Slide 16
Slide 16 text
Start with well architected monolithic
Hooklift, Inc.
The Clean Architecture: https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html
Slide 17
Slide 17 text
Hooklift, Inc.
Image source: http://www.codeproject.com/Articles/1064240/Introduction-to-Software-Architecture
Start with well architected monolithic
Slide 18
Slide 18 text
Know when to split out
Hooklift, Inc.
1. User traffic is higher compared to other parts of the app.
2. A specific context changes too often due to business
requirements.
3. A different team or developer is in charge of a the specific
feature.
4. There might be more patterns that I’m overlooking right
now.
Slide 19
Slide 19 text
Hooklift, Inc.
Have a plan
1. Deployment
2. Configuration
3. Secrets
4. Scaling
5. Metrics and Monitoring
6. Testing
7. Log management
8. Service Discovery
DevOps
Slide 20
Slide 20 text
Foster a DevOps culture
Hooklift, Inc.
Slide 21
Slide 21 text
Cultural change in practices
and communication to
quickly deliver business value
Hooklift, Inc.
DevOps
Slide 22
Slide 22 text
Hooklift, Inc.
1. Is not Docker
2. Is not Terraform
3. Is not Kubernetes
4. Is not Mesos
5. Is not a team or role
DevOps
Slide 23
Slide 23 text
Hooklift, Inc.
DevOps
1. No more tickets for IT to provision virtual machines
2. No more tickets for IT at all
3. Developers own the application and its virtual infrastructure
4. IT trusts and verifies
5. IT joins product teams and stops being in isolation
Slide 24
Slide 24 text
DevOps is a cultural
change
Hooklift, Inc.
Slide 25
Slide 25 text
You must have a DevOps
culture first
Hooklift, Inc.
Slide 26
Slide 26 text
Microservices are not
going to fix a broken
culture
Hooklift, Inc.
Slide 27
Slide 27 text
Thanks!
Hooklift, Inc.
Camilo Aguilar - Founder at Hooklift, Inc.
@c4milo at Twitter and Github