Join David Linthicum for an in-depth discussion in this video What problems need to be solved?, part of Cloud Architecture: Core Concepts.
- [Instructor] So let's talk about understanding the problems that we need to solve when we approach cloud architecture. So, what's important is that we understand requirements are key, so the business requirements, the business case, the technical requirements, the ability to, in essence, address the business in terms of their needs and how they map into a particular technology configuration, either cloud or non-cloud. So we need to understand the "as is" state of things and how we're going to move to the "to be," that's in essence what we're doing. So, in other words, assess everything that they have now, becoming a expert in terms of the business processes and the data that exist within the business currently, and then understand the vision as to where they need to go so what are the business problems you're looking to solve, and how you're going to get to solving those business problems by configuring technology in a different way to solve them.
So the "as is" is what needs to improve, it's really a current state assessment. So the ability to kind of look at the data, look at the processes, look at the people, look at the organization, look at everything and how it's going, and how do you find that out? Well technical documentation, system analysis, independents, in other words you're doing it yourself or you're working with them to do it. And also talking to people, there's a certain human interaction that comes along with being a cloud architect, you have to understand what the business problems are by interviewing individuals.
You'll find that many things aren't necessarily written down or even asked, so you need to figure them out. And then, we're moving to the "to be." How can it be improved? In other words, what things need to happen in order to create a technology solution that's going to be much better than the "as is" state. And then the future state definition, so the ability to kind of define in writing and give to a client or give to your leaders or give to the stakeholders exactly what you see the future really defining and looking like. What is cloud computing going to bring to them? Is it going to be scalability, is it going to be better agility, is it going to be cheaper operational costs? All these things really kind of factor into it, and these are typically documents you create, can be PowerPoint presentations, can be spreadsheets, all of the above, but something that defines what the future state's going to be so we have a meeting of the minds in terms of where we're going and understand how we're going to get there.
And then the technology leverage, we have infrastructure as a service, and all the tools and technology that exists under those particular kinds of cloud like AWS and Google and Microsoft, and software as a service like salesforce.com, security systems like identity access management, DevOps, hundreds of tools that basically exist there, and all other sorts of things that may be relevant, and you'll find that every time you leverage a cloud-based solution and move into a cloud-based architecture, it's always going to be different, it's always going to be a snowflake so to speak in terms of you configuring your technology.
You're going to see the technology over and over again, but the way in which you configure it and the way in which you leverage it and the configuration and the approach you're going to leverage it with is always going to be a bit different.
- Cloud architecture basics
- What problems need to be solved?
- The "as is" and "to be" states
- Cloud storage, CPUs, and databases
- Building your first architecture