Keynote presentation held at Rethink! IT Europe 2017 in London outlining some of the best practices of how to re-invent your IT architecture. Includes key methods like radical agility, microservices and DevOps.

1. LESSONS FROM A STARTUP
Simon Barth, April 2017
IT modernization in action: How to re-invent your IT architecture

2. 2

3. 3
Helping global leaders to reinvent their IT Architecture
2012 20172016201520142013

4. We built a MVP based on the LAMP stack
4
2012
“MVP”

5. We improved service
5
2012 2013
“MVP”
Service &
Quality

6. And ended up with a zoo
6
2012 20142013
SSO &
Microservices
Build
Process
Service &
Quality
...
Single Page
App
“MVP”

7. 7
Upgrade needed

8. 8

9. The keys to achieve the transformation
9
! " #Radical agility Microservices DevOps

10. 10
!Stage 0: Empower your teams

11. 11

12. Principles of Radical Agility
12
PURPOSE
AUTONOMY
MASTERY

13. Radical Agility at Zalando
13Source: https://tech.zalando.com/
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
♂ ♂
Delivery
Lead
People
Lead
$
$
$
$
$
$
♂
Team
Lead

14. 14

15. 15

16. 16

17. 17
"
Cut monoliths into microservices

18. 18

19. Microservices are on the roadmap
19
80 %of surveyed companies bet on microservices

20. Microservices make you faster
20
5xfaster than those who don’t use microservices.
Companies who use microservices deploy

21. But we are not there yet
21
‘We use mostly
microservices‘
9%

22. Monolith Development Lifecycle
22
$ $ $ $
$ $ $ $
$ $ $ $
$ $ $ $
$ $ $ $
Build Test Deploy
Developers Monolith Delivery Pipeline

23. 23
Monoliths: all functionality in one clunky piece

24. Challenges with monolithic software
24
Difficult to
Scale
Long
Cycles
Operations
Issues
Architecture is
hard to maintain
and evolve
New releases
take months
(to test, integrate)
Module X is failing,
Who is the owner?
Lack of
Agility
Lack of
Innovation
Frustrated
Customers

25. Microservices Development Lifecycle
25
$ $ $ $
$ $ $ $
$ $ $ $
$ $ $ $
Build Test Deploy
Build Test Deploy
Build Test Deploy
Build Test Deploy
Developers Microservices Delivery Pipelines

26. 26Image Source: https://www.linkedin.com/pulse/dont-believe-tools-tomasz-cholewa
Microservices: Do one thing, but do it right

27. Microservices pay out for complex scenarios
27Source: Martin Fowler
‘Microservices Premium’
Base Complexity
Productivity
Microservices
Monoliths

28. Example: Monolithic online store
28
ONLINE STORE
Ordering Billing
AccountingInventory
• One piece of Software
• 100k lines of code
• Outdated technology
• Only few developers
understand it
• New releases take
forever

29. Amazon checkout
29

30. Order items on website
30
Checkout
Service
Order
Mgmt
RESTAPI
Postgres MongoDB
3) POST /orders
Inventory
Mgmt
RESTAPI
SAP MM
2) GET /items1) GET /stock
4) POST /items
Application
Interface IT Component
Provider
SAP
Data Object
Orders Items

31. Designing Microservices and selecting technologies
31
Ordering
Inventory
Billing
Accounting
Order Service Billing Service
Inventory Service Accounting Service
SAP FI
Paypal
Order
APIMySQL
MongoDB
Orders Invoices
Stock Items BalancesFinance
API
Inventory
API
Billing
API
Application
Interface
IT Component
Data Object
Bus. Capability

32. Elastic
All new functionality follows our Microservice
Architecture
32
View
Controller
Model
DB
Single Page App
REST-
API
DB
REST-
API
Frontend
Service
Backend
Microservices
Infrastructure
Services

33. Services are independent, which allows scaling
33
Pathfinder
Postgres
Elasticsearch
ArangoDB
Pathfinder UISingle Page App
Backend Services
• GraphQL or REST API
• oAuth2 /w JWT
• Swagger API Docs
• Event-Bus (Webhooks)
Resources
• No sharing across
services
Web-
hooks
MTM Export Images Survey Metrics
Postgres
Kafka
Postgres
Shibboleth
PhantomJS
Postgres
Elasticsearch
InfluxDB
“Platform Services”

34. Most critical tools to build microservices at LeanIX
34
Integrated
Development
Environment
Frameworks
Continuous
Integration
Packaging
Monitoring
IntelliJ
(Java)
VS Code
(Typescript)
Dropwizard
(Java)
Jenkins
Docker
Swagger
(Java)

35. Lessons learned
35
# Services < team size

36. Lessons learned
36
Cut down the original monolith step by step

37. Lessons learned
37
API first: Use self-documenting APIs (e.g. Swagger)

38. Lessons learned
38
Use event based data exchange (e.g. via webhooks)

39. Lessons learned
39
Synchronize data – always allow data to migrate
into the new system

40. Lessons learned
40
Orchestration is really, really important.
Invest in docker container orchestration & deployment
(e.g. Ansible, Kubernetes)

41. Lessons learned
41
For the migration, switch from Scrum to Kanban
to reduce overhead and gain speed

42. Lessons learned
42
Automate the build-test-run process

43. 43
#Add some magic with automated DevOps

44. A shift left of operational concerns
44
Development
Environment
Test
Environment
Stage
Environment
Production
Environment
Continuous
Integration
Continuous
Testing
Continuous
Delivery
Continuous
Monitoring
‘Shift-left‘ of operational concerns

45. LeanIX DevOps setup
45
Develop Build Test Deploy
Develop
Machines
Staging
Server
Production
Servers EU
Docker Hub

46. Wow!
46
3huntil first commit of a new joiner

47. 47
But maybe you are more like him?

48. Four waves to run IT like a startup
48
Single
Source of
Truth
(Existing)
Semi-automatic
Inventory
(Existing)
Microservices
Governance
(PoC)
Fully integrated
Docker &
Kubernetes setup
(in Dev)

49. From idea to production
49
Requirements Capacity & Planning Deployment Monitoring
Microservice Lifecycle Management

50. 50
1
Starting small doesn‘t
mean thinking small

51. 51
2
Join our workshop
to reflect

52. 52
3
Have a chat with
us later J