- [Instructor] All right, let's get started.
and that really is the current state,
in other words, what we have, legacy systems,
And it's important because
So, sometimes this is going to be net new cloud development,
in other words, they don't have any systems
and this is a new company that may be moving into the cloud,
however, we still need to determine the as is state
applications, and problems that need to be solved.
We need to consider the humans.
While we deal with technology exclusively
through a cloud computing architecture,
ultimately, the end results of our labors
that exist within the organization.
Whether that's the stakeholders, the executives,
Finally, you need to consider the business.
And this is foremost something that needs to be
on the top of the mind of every
cloud computing architect out there.
You're there to solve problems that the business has,
you're not there to leverage the best technology,
the state-of-the-art technology,
all-cloud solutions, you know, anything that's hyped,
ultimately this is about backing the appropriate solution
into the needs of the business.
So we need to determine the as is state.
And that means what needs to improve?
Current state assessment.
In other words, where are we now,
and where do we need to be?
And what's the gap between the two?
We need to determine features, functions,
data, process, performance, security,
governance, cost, all those sorts of things.
So, at the end of the day this is about
decomposing things to a functional primitive
and understanding the different aspects of technology.
Security is, obviously, extremely important,
but as is governance, as is performance,
if any of those things don't work up to specifications,
you're going to end up with a failed deployment.
Need to understand users and business requirements,
this means talking to people.
When we go out and understand what the business is doing,
we're not just assessing the computer systems,
we're assessing the people's needs,
we're talking to people.
And also, this is all a good time
for you to be an ambassador for cloud computing,
to explain to people what's going on,
what's likely to change, and how will that change
the way in which they interact with the IT systems.
And then finally the technology you're going to leverage.
So, while I'm not asking you to pre-solve solutions,
in other words come to an as is state assessment
with a pre-determination of
what technologies you're going to leverage
such as Amazon, Microsoft, Google,
as to what technology we're going to use.
Makes the next steps even more easier.
So we have our choices,
we look at the existing state,
including AWS, Azure, Google Platform,
OpenStack, Alibaba, IBM,
any number of different technologies out there
that are being employed.
We look at the APIs, basically the way
in which we're going to interact with those clouds.
Cloud services, we're able to build on top of those APIs.
You know, such as identity, access management, governance,
management and monitoring, databases,
things that cloud providers provide
on top of their base sets of infrastructure services
such as storage and compute.
We're able to leverage things such as cloud service brokers
or cloud management platforms
that sit on top of the cloud services,
which are able to, in essence,
manage those cloud services on our behalf.
We're able to build storage consumers,
people are able to consume storage systems such as S3,
compute consumers, people are able to consume compute,
you know, such as Intel-based cores
and operating systems such as Linux,
database consumers, such as
cloud native databases such as DynamoDB,
or perhaps traditional databases such as Oracle.
And then all able to wrap that up into an abstraction layer
that's able to provide monitoring and management.
And of course security, identity and access management,
and governance need to be a part of that.
So keep in mind that we're in essence
looking at the start of the framework,
so this is a reference model
that you'll see over and over again,
and something you can use as a tool.
You can take this diagram and draw it out,
and associate whatever as is state and to be states
and logical and physical architectures to it
because, in essence, we're solving the problem
by filling in what's in these particular boxes.