Join David Linthicum for an in-depth discussion in this video Complex architectures, part of Cloud Architecture: Advanced Concepts.
- [Instructor] So first the facts. Most of the cloud solutions you're going to design are going to be complex in nature. That's just kind of the nature of the beast. Cloud computing architectures and cloud computing technology is very complex and distributed technology. And so, therefore, you're going to have databases all over the place. You're going to have processes that are all over the place. You're going to have things within the cloud, things on premise. Things that are in a private cloud. Things that are within another cloud that may be different than your primary cloud. And, ultimately, you kind of have to prepare for this complexity.
So, I would love it if the world of cloud architecture was we all move things into a single cloud and basically, it keeps it simple and straightforward. You use common interfaces, common managements, common governance, common security, and things like that. But the real world is different. We have different business problems and business solutions that really push us in different directions. This is not unusual, what you see in front of you. We have an organization perhaps, it's a self-service portal. Operations and admin platform. API integration, kind of the core thing.
And they're leveraging a cloud management platform which is a management layer that sits on top of different resources out there. And it's able to do configuration and automation and governance. Global use of clouds. The ability to categorize services such as microservices. And then, the more important aspect of it is the resource it's able to manage. And you see on the bottom there we have public clouds. Azure, Google, Amazon Web Services. HP, IBM, Rackspace. Private clouds, such as Openstack, Vmware, storage systems.
And then bare metal systems. Such as storage servers that maybe more traditional systems, or legacy systems that exist within the enterprise. So, if you're going to move into cloud architecture you need to understand that the majority of your problem means that you're going to work with and they're going to look more like this. And not basically run a single public cloud, a single private cloud, or no private cloud. And not have traditional systems around. And you have to figure out how you're going to govern it, how you're going to secure it, how you're going to manage it. How you're going to, in essence, take lots of things that are going to make your cloud solution much more durable and manageable as it goes forward.
So, your approach to this should be don't let these things scare you and don't let integrating technology that's different scare you. You should get good at understanding holistically how you're going to place a single paint of blast a self service portal, operations and admin, API integration, things like that above these resources. So, you can manage them effectively as the architect, but more importantly, the operations team and the developers and the people who basically have to make the step work in play have the capability of managing it long-term over time.
But if it gets too complex, we have to put an abstraction layer on top of it or else it's going to be very difficult to manage. That's the (mumbling)
- Microservices and containers
- Complex, disturbed, serverless, and composite architectures
- DevOps integration
- High-performance solutions