Through lecture and hands-on kata exercises, you’ll learn to create cloud-native architectures by applying a rich catalog of patterns that you will be able to leverage regardless of your choice of cloud provider or technology stack. These qualities enhance your ability to apply the cultural and engineering practices of DevOps and continuous delivery and exploit the unique characteristics of cloud infrastructure, helping you eliminate the great conflict between pursuit of business agility and system resiliency and ultimately enabling your survival in a new marketplace where speed is the primary competitive advantage and access to consumer services must be ubiquitous. Matt Stine helps you understand six key architecture qualities: modularity, observability, deployability, testablity, disposability, and replaceability.
There are clear architectural concepts and patterns that you can use as guideposts on your journey to the cloud. Is there any way to make sense of all of the choices and cut through all of the hype?įortunately there is a way forward. Soon you’ll be looking at IaaS versus PaaS, containers versus unikernels, servers versus serverless-the list goes on. Which public cloud provider should you choose? Are you even ready for public cloud, or do you need to focus on private cloud? And what does that even mean? Maybe you’re looking for a hybrid solution. From the start, you face an onslaught of decisions.
Oreilly cloud native java software#
As a software architect, confronting the cloud can feel quite daunting.