Join David Linthicum for an in-depth discussion in this video Understanding common patterns, part of Planning a Multicloud Solution.
- Let's talk about common patterns that were seeing, in looking at use cases of multicloud. So, what's important is that there are major components of mulitcloud that we should review at this point. So in other words, we're starting to see common things that look alike, across the different architectures and macro-architectures, and the micro-architectures, in other words, how we're logically fitting things together, versus how we're creating an application instance to solve a particular business problem. Micro, macro. We're looking for commonalities, and using those as a starting point when building your own architectures.
So, you got to remember these things are like snowflakes. They're always going to be different based on the business needs requirements that you have in your organization. So, it really behooves you to understand the patterns, versus understanding the different solution instances that you see. You're almost never going to be able to copy somebody else's work, because your business requirements and your technology requirements are always going to be unique. This will allow you to consider mos of what's important in macro-use cases, or the architecture. So, let's review.
So again, we have AWS, Azure, Google, openstack, and those can be any of dozens of public clouds, or any of dozens of private clouds, that fits in that box. And the great thing about multicloud, and perhaps the not-so-great thing about multicloud: it's greater than two, but certainly less than infinity, so we can have as many public and private cloud instances, as we need to in this environment. Of course, that puts an unlimited cap on complexity. We have APIs, cloud services, cloud service brokers and cloud management platforms.
We understood those from before. We have a storage consumer, compute consumer, database consumer that we saw in our first video, monitoring and management, and we have security and identity management. So, let's look at this stuff. So, the tech for CMPs and cloud brokers, can be anybody who is able to support these layers of abstraction, which are able to hide resources and services away from you. Either manage them using resource governance based systems, provision them as you needed, and/or broker services.
And they may provide functionality of broker services and cloud management platforms, just cloud management platforms, just cloud service brokers. And ultimately, they're going to be different from each other. So, you've got to understand that the technology that you're going to leverage, whether it's built by HP, whether it's built by CA and VMware, or even native cloud providers such as AWS and Google, they're all going to have their own way of doing it, and they're own proprietary way of doing it. So, you need to understand policy-based cloud monitoring and management, and how that stuff works.
And so, as we're monitoring and managing these various systems, it's not only enough to gather information as to what's going on out there in terms of performance, and in terms of capabilities, and in terms of what is happening in terms of cloud health, but the ability to create policies they're going to react to in a proactive way, to self-heal the system. So, if for some reason, our compute is becoming saturated on the system, we don't have to tell a human about it so they go out and allocate additional servers, virtual servers, we just go ahead and do it automatically based on a policy that we've written, and implemented in our cloud monitoring and management system.
Security, Identity and Access Management Systems, which are AIM for short, and Service Resource Governance are typically always going to be needed in these systems. So, Identity and Access Management Systems are out there and sold by third-party vendors, and those are the ones you want to look at. Those are the ones that are going to be able to span different cloud providers. IF you leverage Identity and Access Management from vendors such as Amazon, obviously they're just going to support their cloud. They may have other hooks for things outside their system or within their ecosystem, but they're really just going to focus on the AWS ecosystem.
Your ecosystem is going to span many different brands of cloud. Therefore, third-party providers that are not locked in to particular cloud technology, and able to leverage multiple cloud technology, are really the way to go
Instructor David Linthicum covers building out operations and development processes; planning governance of resources, cost, and security; putting together a strategy; and staging deployment and testing. He also examines several use cases featuring multiple service providers, showing how these solutions are architected in the real world.
- What is multicloud?
- Use case studies
- Common patterns and problems
- Selecting cloud technology
- Building an operations process
- Building a development process
- Multicloud strategy and planning
- Deployment and testing