Step-by-Step: The Journey to Cloud Native
A Team Perspective by Mike Villiger at Dynatrace, and Kamala Dasika at VMware
Four Things Every Business Needs to Know
- Initiatives to modernize applications to a cloud-native architecture begin with big questions. Where to start? What apps require the most changes? What is the user impact? Organizations looking to modernize should know some of the answers before getting started--for example, how to discover dependencies in applications, how to identify parts of apps that are good candidates for refactoring, how to minimize customer impact during migration, and how to deliver business value through measurable digital transformation.
- Teams building modern apps and microservices are using new techniques to ensure their quality. They are also taking advantage of rapid deployment across build, test, and production cycles. Teams need to know how to contain post-deployment risk. They can do this with rapid rollback of poorly performing releases within blue/green deployments by using AI-based anomaly detection.
- Environments running microservices are highly dynamic and can present a level of complexity in operational data that makes root-cause analysis particularly challenging and time consuming. Teams are overcoming obstacles to manage services at scale by adopting automatic application-environment discovery, service and process flows integrated with platform visibility, and self healing platforms.
- More and more operational decision-making and activity that previously required human intervention is being programmatically driven into platforms. Intelligent automation baked into cloud-native platforms is transforming operations teams into champions of delivering business value. Organizations that want to keep up must understand how to auto-detect apps and services running on multiple clouds, automate problem detection and resolution, identify behavior patterns, anticipate trends and respond quickly, and understand why correlation is not causation.