Running technology is filled with a shiny new object of the day. Some of these technologies are a flash in the pan, while others are transformative. Learn about today's main trends, which are not only changing our infrastructures and applications, but also our organizations and cultures. Today's software systems have become decoupled, often described as microservices, and tend to match organizational and cultural designs. To be agile and decoupled, both the software and the organization must evolve. Analyze some of these new capabilities and why they are becoming critical for today's applications. Key takeaways: o Major reasons and trends driving agility and microservices o How microservices are managed and orchestrated o How microservices change the infrastructure o How this infrastructure should be managed o Which open source technologies (frameworks, governance layers) assist with these new challenges For more information go to: www.appdynamics.com

1. Microservices the modern IT stack:
Trends of tomorrow
Jonah Kowall, VP Market Development and Insights
Twitter: @jkowall

2. APPDYNAMICS CONFIDENTIAL AND PROPRIETARY 2
Notice
The information and materials included in this presentation (collectively, the
“Materials”) are the proprietary information of AppDynamics, Inc. (“AppDynamics” or
the “Company”). No part of the Materials may be reproduced, distributed,
communicated or displayed in any form or by any means, or used to make any
derivative work, without prior written permission from AppDynamics.
The Materials may contain product roadmap information of AppDynamics.
AppDynamics reserves the right to change any product roadmap information at any
time, for any reason and without notice. This information is intended to outline
AppDynamics' general product direction, it is not a guarantee of future product
features, and it should not be relied on in making a purchasing decision. The
development, release, and timing of any features or functionality described for
AppDynamics' products remains at AppDynamics' sole discretion. AppDynamics
reserves the right to change any planned features at any time before making them
generally available as well as never making them generally available.
All third-party trademarks, including names, logos and brands, referenced by
AppDynamics in this presentation are property of their respective owners. All
references to third-party trademarks are for identification purposes only and shall be
considered nominative fair use under trademark law. © 2016 AppDynamics, Inc. All
rights reserved.

9. 9

10. 10

11. Digital agility
The future of business will be
defined by how well companies,
organizations and governments use
technology to engage with partners
and customers across a wide range
of digitalized processes.
...organizations must also confront
the need to change themselves.
Organizational changes, cultural
changes, and shifts in the very
nature of their business will present
the stiffest challenges.
http://gtnr.it/2fxuWnk

12. Future corporate goals: Scalable revenue
• “Gartner predicts that by 2018, 25 percent of new mobile apps will talk to IoT devices”
• As new technologies grow in importance as a way to control and interact with things,
app interfaces will fade
http://gtnr.it/2eFhiRq

13. New interfaces require connectivity and performance
• Is this irritating or unusable to you?
What’s on my calendar
today?

14. Technology influences culture
Your vendors believe this to be the case

15. Really, culture influences technology

16. Centralized versus Decentralized
DevOps creates grassroots empowerment
• Small 1 or 2 pizza teams own a product
• Everyone makes decisions
• Everyone is accountable for full lifecycle
• Agile Dev and Ops
Technology has very little to do with DevOps aside from open and
integration points
Vendors will be happy to sell you 100 units of DevOps

17. Conway’s Law:
Organizations which design systems... are
constrained to produce designs which are
copies of the communication structures of
these organizations.
— M. Conway

18. But… He worked on MUMPS
• MUMPS (Massachusetts
General Hospital Utility
Multi-Programming
System) - Late 1968
• Now called Intersystems
Cache
• Core of Epic EHR which
makes $2b in revenue,
which still looks like it’s
from 1990

19. Monolithic organization
Courtesy of Martin Fowler: http://martinfowler.com/articles/microservices.html

20. Agile organization
Courtesy of Martin Fowler: http://martinfowler.com/articles/microservices.html

21. Microservices aren’t for everyone?
That’s not what I’m reading on the internet
• Everything is not a Sheep
(redis) for example my Dog
(mysql)
• Centralized versus
decentralized data federation
is a major challenge
• Data rearchitecture is difficult
• According to many without
this change you aren’t doing
Microservices

22. New data patterns
Courtesy of Martin Fowler: http://martinfowler.com/articles/microservices.html

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

24. Microservices are at peak hype
• Doesn’t mean
this fits everyone
• Doesn’t solve
people and
process issues
• Culture is key

25. Microservices or Miniservices?
Miniservices = refactored SOA, driven by composition and reuse
Microservices = web-scale SOA, driven by agility and scalability

26. Managing service based apps
• Blinders come on, focus is on me and my team
• Each team owns the lifecycle of a service
• Each team picks tools which work best for them
• Not consistent across teams
• Creates challenges in problem isolation when it traverses a service boundary

27. Managing end user experience in service based apps
• Gathering end user experience metrics in isolation causes issues
with connection to backend.
• Many organizations build another team for this to handle the siloed
nature of the DevOps teams which are service aligned

28. Deploying service based apps
• All the hype just like Hypervizor was, but it doesn’t matter in the long run
• Containers easier to automate
and orchestrate, orchestration is
the key addition
• Tend to be stateless or
immutable in order to
orchestrate
• Orchestration is the key
difference between these
technologies

29. Scaling service based apps

30. 30

31. Future of computing

32. Docker and Cloud
State of the Cloud: DevOps Trends Report 2016
http://bit.ly/2fLauVi

33. Hybrid Orchestration
• Create containers with apps/code (generated from build system)
• Use infrastructure as code to manage the containers and provisioning
in a cloud agnostic manner (Terraform)
• Terraform can deploy on any infrastructure in an agnostic manner
• Kubernetes or Swam can be provisioned and orchestration automated
Next level systems will have to manage across boundaries,
alternately your PaaS can do this for you. They must be fed with
better data from monitoring tools…

34. Edge Computing: Impact, barriers
Copyright © 2015 AppDynamics. All rights reserved.
Fragmented
device support
Interoperability, data
security
Reliance on
cloud
Analyze or
go blind
COMPLEXITY

35. IoT Silos
• All of these new IoT
technologies and
projects have
dependencies on
existing systems…
and the cloud
• Problem isolation just
got even harder
620 professionals involved with IOT within their respective organizations

36. Solutions for tomorrow

37. Information overload ^ 2
Each layer has a tool, which generates too much data
50 VMs
500 Containers

38. 38

39. Graphs and dashboards don’t scale
Analytics?
Who’s doing the
analysis?
You are!

40. At the brink of AI

41. Algorithmic AI Operations (AIOps)
• Rebranding of ITOA with
actual analytics
• Pairing automation with data
and algorithms
• Coupling service
management with monitoring
and automation

42. Please give us your feedback—Session T9215
• Complete the online survey you'll receive via
email later today or via text at:
Text this number: 878787
Text this word: APPSPHERE
• Every time you submit a session survey, your
name will be entered in a random drawing.
We're giving away Amazon Echos
to 5 lucky winners!
• Thank you for your input
APPDYNAMICS CONFIDENTIAL AND PROPRIETARY 42
Win!

43. Thank you