How to re-invent your IT Architecture. André Christ, Co-CEO LeanIX

Transcription

1 How to re-invent your IT Architecture André Christ, Co-CEO LeanIX

2 2012 founded 30 employees > 80 customers 150 % motivated 2

3 OUR MISSION Become global #1 SaaS helping companies to modernize their IT architectures 3

4 Easy to use Fast to implement Open for integration Selected Integrations 4

5 Reduce complexity Ensure compliance Enable growth CUSTOMER USE CASES! Enable Growth Cloud Transformation Monolith to Microservices IoT Architectures " Ensure Compliance Data Compliance (e.g. GDPR) Technology Obsolescence (e.g. SAP Hana) Standards Governance # Reduce Complexity Post Merger Harmonization Application Rationalization Integration Architecture 5

6 Helping global leaders to reinvent their IT Architecture Best-of-class tool for the modern enterprise architecture management The easiest approach to conquer a complex domain

7 How to avoid becoming a Swiss knife? MORE REQUIREMENTS Single-Sign-On (SSO) Custom Data Model Workflows & Surveys Real-time metrics MORE INTEGRATIONS Service Now Apptio SAP Slack 7

8 Microservice: Do one thing, but do it right! 8

9 What is a Microservice? Service-oriented architecture composed of loosely coupled elements that have bounded contexts VP Cloud Architecture Amazon Webservices Former CTO Netflix 9

10 What is a Microservice? Services communicate with each other over the network (internet) Service-oriented architecture composed of loosely coupled elements that have bounded contexts 10

11 What is a Microservice? You can update the services independently; updating one service doesn t require changing any other services. Service-oriented architecture composed of loosely coupled elements that have bounded contexts 11

12 What is a Microservice? Self-contained: You do not need to know the internals of other Microservices, strict interaction via APIs Service-oriented architecture composed of loosely coupled elements that have bounded contexts 12

13 How are Microservices different from a SOA? SOA Microservices Communication SOAP JSON / Binary Service Definition WSDL Swagger / JSON Schema Service Interface Webservice REST-APIs Granularity Medium/Small Small/Micro 1. Fast Networks & Low Latency: Allow high amount of Microservices-Calls 2. Developer Friendly: JSON has reached much larger audience, esp. Web-Developers 3. Pragmatic: Standards set by successful tech companies, not by industry consortiums 13

14 Unparalleled scale and innovation thanks to Microservices 14

15 Microservices are on the roadmap 80 % of surveyed companies bet on microservices Source: LeanIX Survey 15

16 Microservices make you faster Companies who use microservices deploy 5x faster than those who don t use microservices. Source: LeanIX Survey 16

17 Many organizations are not there yet 9% We use mostly microservices 17

18 We have completed our transition to Microservices LeanIX LeanIX View Single Page App Controller Model REST- API REST- API REST- API REST- API REST- API REST- API REST- API Database Pathfinder (2017) MTM (2015) Survey (2015) Metrics (2016) Export (2015) Webhooks (2015) Images (2015) 18

19 1 Agile Process 5 design decisions for our Microservices transition 2 API-First 3 Containerization 4 Automation 5 Event-Sourcing 19

20 1 Agile: Empower your teams 20

21 21

22 The image part with relationship ID rid2 was not found in the file. 22

23 Git-Flow ensures 4-eye principle and continuous learning Pull-Request: Code review of at least one other developer 23

24 24

25 A monolithic architecture would hinder our growth $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ Build Test Deploy Developers Monolith Delivery Pipeline 25

26 Microservices allow us to scale $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ Build Test Deploy Build Test Deploy Build Test Deploy Build Test Deploy Developers Microservices Delivery Pipelines 26

27 2 API-First: Create reliable boundaries 27

28 All our services have REST-APIs documented /w Swagger 28

29 REST-APIs are great but have performance limits Display interactive reports very fast Many requests & unnecessary network load /applications /capabilities GET GET 29

30 Generic REST-APIs create unnecessary effort Allow full customization of data model Uncomfortable generic access to data Provider Data Object User Group GET /factsheets Interface GET /factsheets/<id>/attributes IT Component Application Business Capability GET /factsheets/<id>/relations Tech. Stack Project Process 30

31 Solution: Facebook s GraphQL SQL for APIs Example: One request to build report JSON-based query language to request required data Graph-based access to EA data Strongly typed API for each LeanIX workspace (full multitenancy) query { allbusinesscapabilities { factsheets { id displayname reltochild {factsheet{id}} } } allapplications { factsheets { id displayname reltochild {factsheet{id}} relappltobuscapability {factsheet{id}} } } } 31

32 GraphQL IDE integrated in LeanIX 32

33 3 Containerization: Unify technology usage 33

34 Every Microservice packaged as a Docker Image Resource overhead due to virtualization Efficient packaging and distribution VM VM App A App B Container Container Container Libs Libs svc1 svc2 svc3 Guest OS Guest OS Libs Libs Hypervisor Host OS Server Docker Engine Host OS Server 34

35 Green-Blue Deployment to quickly release functionality Load-Balancer (default = blue) Svc A 1.0 Svc B 1.0 Svc C 1.0 DB, Index, Queue DB, Elastic 35

36 Green-Blue Deployment to quickly release functionality Load-Balancer (default = blue) Svc A 1.0 Svc A 1.1 Svc B 1.0 Svc B 1.1 Svc C 1.0 Svc C 1.1 DB, Index, Queue DB, Elastic 36

37 Green-Blue Deployment to quickly release functionality Test Load-Balancer (default = BLUE) Svc A 1.0 Svc A 1.1 Svc B 1.0 Svc B 1.1 Svc C 1.0 Svc C 1.1 DB, Index, Queue DB, Elastic 37

38 Green-Blue Deployment to quickly release functionality Load-Balancer (default = GREEN) Svc A 1.0 Svc A 1.1 Svc B 1.0 Svc B 1.1 Svc C 1.0 Svc C 1.1 DB, Index, Queue DB, Elastic 38

39 4 Automation: Get efficient in operations 39

40 Highly automated pipeline allows us to deploy every day Develop Build Test Deploy Develop Machines Staging Server Production Servers EU Docker Hub 40

41 Ramp-up of new developers is very efficient 3h until first commit by a new joiner 41

42 Monitoring is critical to ensure enterprise level service Service Description Availability Performance Logfiles Alerting Dashboard Every micro service has a health-check URL Availability Check & Response Time Server Metrics: CPU, Memory, etc. Docker Metrics per Container: CPU, Mem, Browser Metrics: Page Load, JS Errors Central storage for log files Similar for ELK-Stack, but as a Service Single point for all alerts Informs operations managers on duty Dashboard which shows main KPIs Running on Screens in LeanIX Office ELK = Elastic Logstash Kibana 42

43 5 Event-Sourcing: Integrate with the world 43

44 Subscribe to every change in the LeanIX inventory 44

45 Internally we use Apache Kafka for Event distribution 45

46 Quickly integrate LeanIX with other tools, e.g. Slack 46

47 You can t build your IT architecture today with yesterday s tools and stay in business tomorrow 47

48 Thank you % christ_andre