Containers and Microservices Create New Performance Challenges

Transcription

1 Containers and Microservices Create New Performance Challenges Cloud Computing Expo Santa Clara, 2015 Jonah Kowall, VP Market Development and Insights

2

3 Software is eating the world Emergence of the Software-Defined Business CIOs must enhance customer engagement with continuous business services. CIOs: Stop Wasting Your Time 2015 CIOs must balance future needs with today s operational realities. Tech Trends The Fusion of Business and IT Businesses must think and act differently to succeed in this new environment. Accenture Technology Vision 2015 All industries in all geographies are undergoing radical digital disruption. Gartner, The 2014 CIO Agenda Copyright 2015 AppDynamics. All rights reserved. 3

4 PREY Rate of innovation will determine if you are the predator or the prey PREDATOR 52% of Fortune 500 firms since 2000 are gone

5 WHAT IS A MICROSERVICE?

6 Microservices are an approach to developing a single application as a suite of small, connected, services Martin Fowler Loosely coupled service orientated architecture with bounded contexts Adrian Cockcroft In computing, microservices is a software architecture style in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task, facilitating a modular approach to system-building. Wikipedia

7 Monolithic versus microservices architecture Courtesy of PWC: Copyright 2015 AppDynamics. All rights reserved. 7

8 Down with the monolith Intimidates developers with complexity Long ramp time Heavy change process IDE and dev environments are difficult to manage and setup Scalability is a challenge due to rigid design Long term language and technology stack commitment Stagnation High cost

9 Properties of microservices architecture Flexibility The services are easy to replace Services are organized around capabilities Services can be implemented using different programming languages, databases, hardware and software environment, depending on what fits best Architectures are symmetrical rather than hierarchical (producer - consumer)

10 Example : e-commerce site microservices Front-end components Catalog services Inventory management Shipping Payments Billing Notifications Search agent User profile

11 WHY ARE PEOPLE SHIFTING TO MICROSERVICES?

12 Agile Teams Each service is a product Designed for failure Autonomous teams

13 Monolithic organization Courtesy of Martin Fowler:

14 Agile organization Courtesy of Martin Fowler:

15 Applications are transforming Conventional Enterprise Central SQL Database Sticky In-memory Session Chatty Protocols Tangled Service Interfaces Polled Information Fat Complex Objects Components as Jar Files Java,.NET Cloud "Native" Pattern Distributed Key/Value NoSQL Shared Memcached/Redis Session Latency Tolerant Protocols Layered Service Interfaces Event-driven Lightweight Serializable Objects Components as Services JavaScript, Python, Ruby, node.js Adapted From Cloud Architecture Tutorial by Adrian Cockcroft (Netflix) Copyright 2015 AppDynamics. All rights reserved. 15

16 Team technology choice Can use any technology in services since they are short lived and easily rewritten

17 New data patterns Courtesy of Martin Fowler:

18 Challenges Most are horrible at automation Automation is fragmented Many moving parts must be coordinated You must master good engineering practices

19 WHAT IS DOCKER?

20 Hypervizor vs docker Courtesy of IBM (SoftLayer):

21 Why are people switching to docker Easy to package Easy to run anywhere (Smaller footprint) Fast -> Launch and Kill Linux or Windows (in Server 2016 Preview) Can use on Windows client and OSX for dev with boot2docker Basic contained configuration in DockerFile Less tools to manage each container

22 Performance: boot time 7 Average Server Boot Time Time in Seconds docker KVM 1 0 docker KVM Courtesy of IBM (SoftLayer):

23 Performance: reboot time Average Server Reboot Time Docker 18.9x faster Time In Seconds docker KVM docker KVM Courtesy of IBM (SoftLayer):

24 Performance: memory speed Memory Benchmark Performance MiB/s BareMetal docker KVM MEMCPY DUMB MCBLOCK Memory Tests Courtesy of IBM (SoftLayer):

25 Performance Summary CPU and Network are the same Flexible deployment Runs on desktops and developer systems

26 WHAT MONITORING CHALLENGES MICROSERVICES CREATE?

27 Application End User Experience complexity = is Business exploding Transactions Performance Agile Login Flight Status Search Flight Purchase Mobile Web SOA Cloud NOSQL Copyright 2015 AppDynamics. All rights reserved. 27

28 End-to-end visibility of business transactions Real User Synthetic Browser & Mobile MONITORING Application Performance Management Java,.NET, Python, C/C++, PHP, Node.js Database MONITORIN G Server MONITORING Copyright 2015 AppDynamics. All rights reserved. 28

29 Current open source options cadvisor Docker metrics only ELK stack Lots of moving parts Only handles log data (Docker, app logs, etc) Agent per host Sensu Need RabbitMQ, Redis, Sensu Handles metric data only (Docker, host, other plugins) Agent per host Up and coming : Prometheus, Spigo NO TRANSACTION TRACING! NO END USER VISIBILITY!

30 Current commercial options Stack of APM, infrastructure, log analytics Splunk +New Relic, Dynatrace, Ruxit +SevOne, ScienceLogic, Zenoss AppDynamics (1 install/ui for APM, infrastructure, log) SaaS or on premises Same product

31 HOW IS COMPLEXITY CAUSING MANAGEMENT ISSUES?

32 Today s tools exist within silos Mobile/Web App Middleware Database Server Network Storage CMDB Limited Integrations Incomplete & Inaccurate Copyright 2015 AppDynamics. All rights reserved. 32

33 Difficult to connect the dots without context Checkout Transaction Mobile/Web App Middleware Database Server Network Storage?? Checkout is slow JVM perf issues Slow SQL query Network 97% Copyright 2015 AppDynamics. All rights reserved. 33

34 Reactive problem identification Checkout is Slow L1 Troubleshoot Escalate L2 Troubleshoot Escalate War Room Resolution Long time to troubleshoot and resolve issues Time No end-to-end perspective No situational awareness

35 Transaction Tracing

36 Visualize microservices/docker application

37 Visualization with OSS/spigo (simulated)

38 Managing services

39 Key takeaways Treat performance as a feature Create a performance budget with milestones, speed index, page speed Capacity plan and load test the server-side Optimize and performance test the client-side Monitor performance in development and production Instrument everything Measure the difference of every change Understand how failures impact performance Make monitoring critical and test in your continuous delivery process Connect the biz/dev/ops performance perspectives to align on business impact metrics and KPIs

40 QUESTIONS?

41 Thank You