Fed up with stop and go in your data center? Shift into overdrive and pull into the fast lane! Learn how AutoScout24, the largest online car marketplace Europe-wide, are building their Autobahn in the Cloud. The secret ingredient? Culture! Because “Cloud” is only one half of the digital transformation story: The other half is how your organization deals with cultural change as you transition from the old world of IT into building microservices on AWS with agile DevOps teams in a true „you build it you run it“ fashion. Listen to stories from the trenches, powered by Amazon Kinesis, Amazon DynamoDB, AWS Lambda, Amazon ECS, Amazon API Gateway and much more, backed by AWS Partners, AWS Professional Services, and AWS Enterprise Support. Key takeaways: How to become Cloud native, evolve your architecture step by step, drive cultural change across your teams, and manage your company’s transformation for the future.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Christian Deger, Chief Architect, AutoScout24, @cdeger
Constantin Gonzalez, Principal Solutions Architect, AWS, @zalez
December 1, 2016
The Enterprise Fast Lane
What Your Competition Doesn't Want You to Know
About Enterprise Cloud Transformation
JKT303

2. What to expect from this session
• How to become cloud native
• How to transition from “difficult to change” to
evolutionary architecture
• How to drive cultural change across your organization
• Real-world enterprise IT transformation experience
• Tools and ideas for your own digital journey

3. New IT
• Unlimited resources
• No financial risk
• Software-defined,
dynamic architecture
• 100% automated
• Flexible
• Deployed in minutes
• World-wide
• Secure
• Robust

4. Cloud =
no physical
limitations

5. Cloud promises
•Lower cost

6. Cloud promises
•Lower cost
Visit:
ARC313 Running Lean Architectures:
How to Optimize for Cost Efficiency

7. Cloud promises
•Lower cost
•Better agility

8. Agility

9. Agility
• Technical agility

10. Agility
• Technical agility
• Organizational agility

11. Culture

12. Christian Deger
Chief Architect
cdeger@autoscout24.com
@cdeger

13. 2.4 million
vehicles

14. 2000 servers
2 data centers
MTBF optimized

15. Development
“Change”
Operations
“Stability”
Dev and Ops Silos

16. ***

17. New
CEO

18. talent?
Do you attract

19. 21st century
What does a
tech company
look like?

21. Great design
Universally connected
Mobile first
Instant business value
Massive data insight
Highly available

22. good, but not great
Hmm, we are

23. Reboot
everything

24. .NET/Windows to JVM/Linux
Monolith to microservices
Data center to AWS
Devs + Ops to collaboration culture
Involve product people

25. “Death Star” diagrams
Amazon 2008 Twitter 2013

26. http://scs-architecture.org/
Self-contained systems = microservices flavor
Team 1
Team 2 Team 3
One business
capability is
owned, built
and run as an
SCS by one
team.
Self-contained
systems are
vertical slices
integrated at
the UI.

27. Same
direction

28. STRATEGIC
GOALS
Goals of the business side
ARCHITECTURAL
PRINCIPLES
High-Level Principles
DESIGN AND DELIVERY
PRINCIPLES
Tactical measures
REDUCE TIME TO MARKET
Establish fast feedback loops to learn, validate and
improve. Remove friction, hand-offs and undifferentiated
work.
MOBILE FIRST
Start small and use device capabilities.
SUPPORT DATA-DRIVEN DECISIONS
Provide relevant metrics and data for user and market
insights. Validate hypothesis for problems worth solving.
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. Make boundaries
explicit. Inverse Conway Maneuver.
LOOSELY COUPLED
By default avoid sharing and tight coupling.
No integration database. 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 built solutions.
DATA-DRIVEN/METRIC-DRIVEN
Collect business and operational metrics. Analyze, alert
and act on them.
ELIMINATE ACCIDENTAL COMPLEXITY
Strive to keep it simple. Don’t over-engineer.
Focus on necessary domain complexity.
AUTONOMOUS TEAMS
Make fast local decisions. Be responsible. Know your
boundaries. Share findings.
INFRASTRUCTURE AS CODE
Automate everything: Reproducible, traceable, auditable
and tested. Immutable servers.
CROSS-FUNCTIONAL TEAMS
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.
Fail fast, recover and learn. Optimize for MTTR not MTBF.
SECURITY, COMPLIANCE AND DATA PRIVACY
Build with least privilege and data privacy in mind.
Know your threat model. Limit blast radius.
COST EFFICIENCY
Run your segment in the right balance of cost and value.
ONE SCOUT IT
Foster collaboration. Harmonize and standardize tools.
Pull common capabilities into decoupled platform services.
Version 2.0
Icons made by Freepik from www.flaticon.com are licensed under CC BY 3.0
BEST TALENT
Autonomy, purpose and mastery: We know why we do
things, we decide how to approach them and deliberately
practice our skills.

29. Build
MeasureLearn

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

31. Autonomous teams
business capabilities
organized around

32. You build it,
you run it.

33. We are all
engineers!

34. Follow the
trail

35. Guilds
Self-organizing; common interests; across teams
Macro architecture, infrastructure, front end, QA...
Beware of Mandelbrot teams

36. Continuous
delivery

37. Application code in
one repository per
service.
CI
Deployment
package as
artifact.
CD
Deliver package to
servers
Delivery pipeline—data center

38. Application code
and infrastructure
specification in one
repository per
service.
CI
Deployment
package and
infrastructure
declaration as
artifact.
CD
1. Create or update
service infrastructure.
2. New instances pull
down package and
start application.
Delivery pipeline—AWS

39. Cattle,
not pets

41. Hamburgers,
not cattle

42. Event streaming

43. Monitoring is the new testing

44. No
staging
environment

45. Learners
Experienced
Ramp up
First 8 teams: Split teams to share knowledge

46. Learners
Experienced
Ramp up
Plan for next teams: Coach don’t split
Coaching

47. 015 Teams
025 Lambda functions
200 Repositories
040 Microservices
009 Systems
Status quo

48. New service
service boostrapping1/2 day
front end3 days
back end4 days
cycle time20 minutes

49. Idea
ProductData
build
measure
learn
The innovation cycle

50. Idea
ProductData
build
measure
learn
Cloud
Microservices
CI/CD
Big Data
IoT
Mobile
Analytics
BI
Machine Learning
The Cloud enables technical agility…

51. Idea
ProductData
build
measure
learn
Cloud
Microservices
CI/CD
Big Data
IoT
Mobile
Analytics
BI
Machine Learning
Lean
Agile
DevOps
…and culture enables organizational agility

52. Thank you!
cdeger@autoscout24.com, @cdeger
glez@amazon.de, @zalez

53. Picture Credits
Wandergeselle by Sigismund von Dobschütz, licensed under CC-BY-SA-3.0
"HotWheels - '69 Ford Torino Talladega“ by Leap Kye, licensed under CC BY-ND 2.0
Enterprise IT Adoption Cycle 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
Stopwatch by William Warby under CC BY 2.0

54. Remember to complete
your evaluations!