Join David Linthicum for an in-depth discussion in this video Going beyond basic architecture, part of Cloud Architecture: Design Decisions.
- [Instructor] Let's talk about what we're saying when we're moving beyond the basic cloud computing architecture. First we'll look at what's important. Let's take things from the design decisions to more advanced cloud architectural concepts. Ultimately, this is about your ability to understand and make the correct choices in terms of resources that you're putting in place to make your cloud architecture work. This is holistic in nature, we need to understand what's there, what cloud services are available, what on premise services are available, and what tools, technology, is available to you as an arsenal of tools that you can leverage to make your cloud computing architecture work well.
This is core of what you do as a cloud architect. You make decisions. This is all about making the right decisions, or as many of the right decisions as you can make based on the information that's available. Keep in mind that this is not an exact science, this is more art. The fact of the matter is, is that you're dealing with technology that's typically new, hasn't been proven yet in the enterprise, and you're trying to make decisions as to what technology will have the most value for your particular application. Pulling things together.
We have the cloud-based systems, basically the public clouds like AWS, Microsoft, Google. We have the requirements on what those cloud-based systems should look like, the technology that needs to go into those cloud-based systems, the security, the governance, and DevOps. We have all these external requirements that are coming in at us in doing the architecture. We need to understand the business requirements which really should lead you to what kinds of systems you're gonna build on the public clouds like AWS, Microsoft, and Google.
The technology you're gonna leverage. Is it gonna be machine learning? Is going to be serverless technology? Security, encryption, identity access management. Governance, could be service level governance, or governing the APIs, or it could be resource level of governance where we're governing storage and compute systems, things like that. And of course, DevOps, the ability to apply development and operations as really kind of the ability to change the applications, and change the workloads, and change the databases on these cloud-based systems you're building, the core architecture.
There's three courses. Number one will take you through core concepts which you may have taken already. From there, we're gonna go to design decisions, and then advanced concepts.
- Advanced architecture concepts
- Building a business case
- Defining storage, processing, and other requirements
- Mapping requirements
- Performance and security