The document discusses strategies for transitioning from a monolithic architecture to microservices in cloud environments, emphasizing the importance of collaboration culture and autonomous teams. It outlines key principles such as data-driven decision-making, accountability, and infrastructure as code, alongside the need to ensure security, compliance, and streamlined operations. Central to this approach is optimizing for fast feedback, eliminating complexity, and making teams responsible for their products.

1. GOTO Nights Berlin | 03.05.2016 | Christian Deger
Highway to heaven
Building microservices in the cloud

2. Christian Deger
Architect
cdeger@autoscout24.com
@cdeger

3. 2,4 Million Vehicles

4. 17 countries
350 employees
140 in IT
RUS
S
PL
NL
D
B
F A
HR RO
BG
UA
I
TR
E
CZ

5. 2000 Servers
2 Data Centers
MTBF optimized

7. New
CEO

8. Talent?
Do you attract

10. good
Hmm, we are

11. Reboot
everything

12. Project
Tatsu

13. .NET / Windows to JVM / Linux
Monolith to Microservices
Data center to AWS
Devs + Ops to Collaboration culture
Involve product people

15. same
direction

16. STRATEGIC
GOALS
Goals of the business side
ARCHITECTURAL
PRINCIPLES
High-Level Principles
DESIGN AND DELIVERY
PRINCIPLES
Tactical measures
REDUCE TIME TO MARKET
Speed, Fast Feedback
COST EFFICIENCY
Collect metrics to allow decisions cost vs. value.
SUPPORT DATA-DRIVEN DECISIONS
Listen to users and validate hypothesis.
Provide as many relevant metrics & data as possible.
YOU BUILT IT, YOU RUN IT
The team is responsible for shaping, building, running and
maintaining its products. Fast feedback from live and
customers helps us to continuously improve.
ORGANIZED AROUND BUSINESS CAPABILITIES
Build teams around products not projects. Follow the
domain and respect bounded contexts. Inverse Conway
Maneuver.
LOOSELY COUPLED
By default avoid sharing and tight coupling, except for the
big things in common. Don’t create the next monolith.
MACRO AND MICRO ARCHITECTURE
Clear separation. Autonomous micro services within the
rules and constraints of the macro architecture.
AWS FIRST
Favor AWS platform service over managed service, over
self-hosted OSS, over self-rolled solutions.
DATA-DRIVEN / METRIC-DRIVEN
Collect metrics from processes and applications. Analyze,
alert and act on them.
ELIMINATE ACCIDENTAL COMPLEXITY
Strive to keep it simple. Focus on essential complexity.
You build one, you delete one.
AUTONOMOUS TEAMS
Make fast local decisions. Be responsible. Know your
boundaries. Share findings.
INFRASTRACTURE AS CODE
Automate everything: Reproducible, traceable and tested.
Immutable servers over snowflake servers.
COLLABORATION CULTURE
Engineers from all backgrounds work together in
collaborative teams as engineers and share
responsibilities. No silos.
BE BOLD
Go into production early. Value monitoring over tests.
Recover and learn. Optimize for MTTR not MTBF.
SECURITY, COMPLIANCE AND DATA PRIVACY
Security must be included from the beginning and
everybody’s concern. Keep data-privacy in mind.
CONTAINMENT AND BOUNDARIES
Align blast radius and vendor lock-in with the boundaries of
the organization or business capabilities.
Version 1.0
Icons made by Freepik from www.flaticon.com are licensed under CC BY 3.0

17. Autonomous teams
business capabilities
organized around

18. collaboration culture

19. We are all
engineers!

20. You build it,
you run it.

21. Continuous
Delivery

22. Unlimited Infrastructure with APIs

24. Immutable
Servers

25. Monitoring is the new testing

26. Separate
code deployment
feature release
from

27. How many environments?
Which versions on staging?
Prod differs anyway: Load, data, patterns
V2V3
V6 V5
V4
V7
V5
V8
Engineer CI Dev Staging
V1
V4
Prod

28. No
staging
environment

29. Event Sourcing
one way data highway
and data pumps

30. SQS + S3
Kinesis + S3
Kinesis + DynamoDB
SQS + DynamoDB
Proxy + DynamoDB
DynamoDB
Evolution

31. How (not) to share
shared nothing as default
loosely coupled
fast local decisions
voluntary adoption
exception: macro concerns

32. Frontend integration
Loosely coupled
Autonomous team
High optimization

34. PageSpeed Module
css (page+fragment)
js (page+fragment)
ngx_pagespeed
css (page)
js (page)
css (fragment)
js (fragment)

35. Infrastructure guild
Agree on things to do
Share learnings
Delegate implementation to teams
Infrastructure product teams needed?

37. STRATEGIC
GOALS
Goals of the business side
ARCHITECTURAL
PRINCIPLES
High-Level Principles
DESIGN AND DELIVERY
PRINCIPLES
Tactical measures
REDUCE TIME TO MARKET
Speed, Fast Feedback
COST EFFICIENCY
Collect metrics to allow decisions cost vs. value.
SUPPORT DATA-DRIVEN DECISIONS
Listen to users and validate hypothesis.
Provide as many relevant metrics & data as possible.
YOU BUILT IT, YOU RUN IT
The team is responsible for shaping, building, running and
maintaining its products. Fast feedback from live and
customers helps us to continuously improve.
ORGANIZED AROUND BUSINESS CAPABILITIES
Build teams around products not projects. Follow the
domain and respect bounded contexts. Inverse Conway
Maneuver.
LOOSELY COUPLED
By default avoid sharing and tight coupling, except for the
big things in common. Don’t create the next monolith.
MACRO AND MICRO ARCHITECTURE
Clear separation. Autonomous micro services within the
rules and constraints of the macro architecture.
AWS FIRST
Favor AWS platform service over managed service, over
self-hosted OSS, over self-rolled solutions.
DATA-DRIVEN / METRIC-DRIVEN
Collect metrics from processes and applications. Analyze,
alert and act on them.
ELIMINATE ACCIDENTAL COMPLEXITY
Strive to keep it simple. Focus on essential complexity.
You build one, you delete one.
AUTONOMOUS TEAMS
Make fast local decisions. Be responsible. Know your
boundaries. Share findings.
INFRASTRACTURE AS CODE
Automate everything: Reproducible, traceable and tested.
Immutable servers over snowflake servers.
COLLABORATION CULTURE
Engineers from all backgrounds work together in
collaborative teams as engineers and share
responsibilities. No silos.
BE BOLD
Go into production early. Value monitoring over tests.
Recover and learn. Optimize for MTTR not MTBF.
SECURITY, COMPLIANCE AND DATA PRIVACY
Security must be included from the beginning and
everybody’s concern. Keep data-privacy in mind.
CONTAINMENT AND BOUNDARIES
Align blast radius and vendor lock-in with the boundaries of
the organization or business capabilities.
Version 1.0
Icons made by Freepik from www.flaticon.com are licensed under CC BY 3.0

38. Picture Credits
• "HotWheels - '69 Ford Torino Talladega“ by Leap Kye, licensed under CC BY-ND 2.0
• Differences between Traditional vs Next Generation by Simon Wardley under CC BY-SA 3.0
• Enterprise IT Adoption Cycle by Simon Wardley under CC BY-SA 3.0
• And the future is private by Simon Wardley under CC BY-SA 3.0
• Leosvel et Diosmani by Ludovic Péron under CC BY-SA 3.0
• Spare wheel by Brian Snelson under CC BY 2.0
• Wheel clamps Texas by Richard Anderson from Denton, United States (Boots.) under CC BY-SA 2.0
• Wandergeselle by Sigismund von Dobschütz under CC BY-SA 3.0
• Sharing Sucks (4536747557) by eyeliam from Portland, United States under CC BY 2.0
• Traffic Jam by Doo Ho Kim under CC BY-SA 2.0
• Puzzling by Bernd Gessler (Own work) CC BY-SA 3.0
• Amazon16 by Neil Palmer/CIAT under CC BY-SA 2.0

39. Backup

41. 21st Century
What does a
tech company
look like?

42. Great Design
Universally Connected
Mobile First
Instant Business Value
Massive Data Insight
Highly Available

43. Giants
Stand on the
Shoulders of

45. Conway’s Law
“organizations which design systems ... are
constrained to produce designs which are
copies of the communication structures of
these organizations”

46. Unified
Logs
CC

47. Two stacks
Cash stack meets shiny new stack
One company
Lights on in cash stack
Feature freeze
Where to build new features?
Ease of integration helps business people
WW