You're asked to build more changeable, available, scalable, and secure software. While cloud platforms make some of those characteristics easier to achieve, it's more about *how* you build software, not *where* you run it. In this course, Cloud-native Architecture: The Big Picture, you'll learn what it means to be cloud-native. First, you'll look at the core principles behind cloud-native software. Next, you'll dive into the key patterns that help us create better software. Finally, you'll review enabling technologies that realize those patterns. When you're finished with this course, you'll have a strong understanding of what you need to do in order to start building cloud-native software.
Richard Seroter is a Senior Director of Product for Pivotal, a 10-time Microsoft MVP for
cloud/integration, an instructor for developer-centric training company Pluralsight, the lead InfoQ.com editor for cloud computing, and author of multiple books on application integration strategies.
Course Overview Hey everyone. My name is Richard Seroter, and welcome to my course, Cloud-native Architecture: The Big Picture. I'm a senior director of product at Pivotal, an 11-time Microsoft MVP, and lead editor for the cloud topic at infoq. com. If you're an established company that isn't all in on the public cloud, and honestly, few are, does that mean you can't be a cloud native? Nope. In this course, we're going to debunk that myth and show that cloud native is about how, not where. Some of the major things we're going to include are the core principles behind the ideas of cloud native and how industry leaders define it. We're going to look at the application, infrastructure, deployment, and team-driven patterns that represent cloud-native ideals. And then we'll review the technologies that cloud natives use to deliver better software. By the end of this course, you'll know what it means to be a cloud, and more importantly, what ideas you can start incorporating today to build and operate software that matters. I hope you'll join me on this journey to learn what it means to be cloud native with this big picture course, at Pluralsight.
The Patterns of Cloud-native Architecture Hey, my name is Richard Seroter. We're in a course about cloud-native architecture. This module focuses on the patterns you'll apply in your journey to become a cloud native. First off, we're going to spend some time on application architecture patterns, what are the things you have to think about when you're building the software. Then we'll switch and look at application delivery patterns, what does it mean to build and ship that software to production. We'll also discuss some application infrastructure patterns, the thing that really are any environment that your software runs in. Then finally, we'll look at application team patterns as you're actually functioning as a team, what are some of those core things you're going to want to do to support those other areas. And then we'll wrap up summarizing some of the patterns we've discussed in this module. As a reminder, using my definition, cloud-native software is built for scale, built for continuous change, built to tolerate failure, and built for manageability. If you do those sorts of things, you're moving in a cloud-native direction.
The Technologies for Cloud-native Architecture Greetings. I'm Richard Seroter. Welcome to this module in a course about cloud-native architecture and introducing you to some of the patterns and technologies to be successful here. In this module, we're going to start by looking at application architecture technologies. We're going to look at application delivery technologies next, then application infrastructure technologies before we look at application team technologies and wrap up. This will complement the previous module where we looked at the patterns for each one of these categories. Now let's look at some of the tech that helps you realize those patterns. And again, as a reminder, we think of cloud-native software, we're building software that's capability of scale, that's going to comfortably scale, that can change easily, that's built to be changed, that can easily tolerate failures, and it's built for manageability, something that can sustain day after day, month after month.