Register Here:
https://info.dynatrace.com/apm_dtm_cld_17q3_wc_journey_to_cloud_na_registration.html
Application modernization is critical to avoiding digital disruption. In a recent study conducted by Deloitte and the MIT Sloan Management Review, 87 percent of executives responded that they believed digital technologies will disrupt their industry. Yet, only 52 percent of CIOs say their ability to address this threat does not exist or is in the process of being built over the next 2 years.*
Join Alois Mayr, Tech Lead for Cloud and Virtualization technologies in the Dynatrace Innovation Lab, to discuss a 3-step path to modernizing applications and the unique benefits Dynatrace provides along the journey. Among the topics to be discussed include: how to achieve digital transformation success with key observations and patterns, best practices followed by companies who have achieved this successfully, and how to ensure minimal customer impact while implementing a cloud migration project.
During the webinar you will learn how to:
Manage highly dynamic larger-scale microservices without increasing operational costs. Enable efficient & effective delivery with a consistent set of metrics across the entire software delivery pipeline.
Allow application teams to collaborate, adapt and adjust based on the same information, from commit to production, with a complete feedback loop.
Automate monitoring and focus on innovation, even in polyglot development environments.
Ensure minimal customer impact during cloud migration and oversee ALL facts for cost optimization of cloud applications.
In seconds, identify problems and pinpoint to the underlying root causes using artificial intelligence.
*Deloitte: Navigating legacy: Charting the course to business value, 2016-2017 global CIO survey.
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Â
The Journey to Cloud Native - A 3-Step Path to Modernizing Applications [Webinar Replay]
1. Journey to Cloud Native
A Three Step Path to Modernizing Applications
Alois Mayr, Technology Lead Cloud & Containers
@mayralois
2. The future is ⌠now
bash-3.2$ cf target -s prod
API endpoint: https://api.cf.$DOMAIN
User: amayr
Org: dynatrace
Space: prod
bash-3.2$ cf push
3. The cloud-native evolution
9 out of 10
of surveyed respondents are going to
migrate to cloud technologies
within the next five years
Get your copy https://info.dynatrace.com/apm_all_wp_cloud_native_evolution_en_registration.html
4. ..but what does it mean to be cloud native?
Container packaged - isolated unit of application deployment
Dynamically managed - central orchestration process
Micro-services oriented - loosely coupled, explicit dependencies
Source: Cloud Native Computing Foundation
5. ..but what does it mean to be cloud native?
Source: Pivotal.io
6. ..but what does it mean to be cloud native?
Onsi Fakhoui: VP Cloud Research & Development
7. Bimodal IT
Not every project is a cloud project, but cloud thinking is everywhere
13. We see three different stages how
companies embrace transformation
The journey to become cloud-native
14. Stage 1: First steps into the cloud by CD
âLift and Shiftâ to modern platforms
Applications stay the same
Release speed massively increases
Automation is key
16. Control code complexity
N+1 interaction patterns - control flow design
More than 10 service hops - hard to debug
Highly asynchronous - hard to understand
Unusual Log Activity
18. Stage 2: Refactoring towards micro services
First micro services
Scheduling and orchestration
Architectures become polyglot
Independent release cycles
19. Writing fast cloud native applications
Rule #1: Donât write slow code
Rule #2: Donât write code that doesnât scale
20. Control environment complexity
Service call payload - < 200 kb
Chatty services - > 50 service calls
Inter-tier heavy interactions - granularity and locality
Status codes - only OK is 200
27. Watch your application live
Health monitoring â symptoms
Orchestration monitoring - causality
Application monitoring - root cause
28.
29. 7:00 a.m.
Low Load and Service running
on minimum redundancy
12:00 p.m.
Scaled up service during peak load
with failover of problematic node
7:00 p.m.
Scaled down again to lower load
and move to different geo location
Deployments are no longer static
30. You donât fly by hand here
820 Billion
dependencies
Network Problem
Mushroom cloud effect
Ops are no longer deploying apps, they rather need to provide the underlying platform to self-service teams. Ops become âOps as Serviceâ
Itâs also about how you compute within your data center or cloud. As you move toward apps of innovation you will also move toward software-defined data centers. If youâre using the public cloud everything is soft-wired already, but maybe in your data centers youâre looking toward VXLAN or other means to turn your current hard-wired networking into software. And not only networking, but also how you provision systems, how you make them accessible on a self-serve basis to groups like your engineering teams. In many ways your data center is turning into an API and youâre becoming a cloud provider.
Discussion questions:
Are you moving toward self-service for your engineering teams?
Do you see your data center team as becoming a cloud operations team?
Letâs talk about about the role of the network: the migration from a monolithic to a to microservices-oriented architecture involves trading fast in-memory communication for slower inter-service communication across networks. This can quickly become an issue if a) services are chatty (not too well-defined) or b) services are too fine-grained (you are taking the âmicroâ in microservices too seriously): the higher the degree of distribution, the more communication over the wire.
What if the network infrastructure itself becomes a limiting factor?
B2W example.
9 applications are HEALTHY!!!! only services have issues, but thats fine.
3300 servics running on 10k JVMs
on just 142 hosts
thats no longer for human doing visual monitoring; ist ideal for intelligent monitoring systems to deal with