- [Man] K. Let's talk about the particular levels
of the architecture. We're going to talk about
storage level first. So, what's important here, is that
when understanding requirements, we need to move
through a checklist, we need to go from the most primitive
things typically, but, you can do this out of order
the most sophisticated thing, you'll find that cloud
is really a mix of things, such as storage you compute
and networking, which are primitive level functions
basic, architectural functions, infrastructure functions
up to feature functions, things that are more sophisticated
such as machine learning, server less computing, things
that are more advanced. So we're going to work
from the primitives to the applications and the processes
as I stated. So ultimately this is about us moving
up from infrastructure into feature functions and services
into the applications and then into monitoring deb ops
So cloud architecture, we have the application level
we have the network level, we have the processing level
we have the data level, and we have the storage level
and that's what we're going to start with.
Within the storage level we have a couple of things
to consider. We have the physical storage and
the logical storage. The physical storage is
probably most interesting to us because it's actually
where we physically store the information and data
and from earlier in this course we saw the differences
between object, file and block level storage
and ultimately you need to, in essence,
pick one, two, sometimes all three
of the physical storage approaches to
figure out how to do your architecture.
Logical storage is the ability to
leverage storage through an abstraction layer
So ultimately, we're not necessarily
talking directly to a physical storage level
that exists within the cloud but were talking through
an abstraction layer which may remap
or reproduce storage in a certain way
that makes more sense for the business or more sense
for the physical storage system that we're using
so it allows you in that sense remove the complexity
from very complex storage type systems
and look at it logically. So the storage level
we have physical storage, logical storage and kind of
breaking that down a bit we have object, file and block
and then, we have the particular providers of the storage
systems, in this case, object. And we have AWS, Google
and Microsoft. There could be others and, by the way,
you may use certain cloud systems that may not be
listed here that may be not as high in the market but
you know, certainly are there to solve your issues.
So, consider the fact that were moving from the
storage level to the physical storage level
to the object level and then down to the particular
object storage provider. Then we can do the same thing for
file and the same thing for block and the same
thing for logical. So and then we look at
another breakdown of, in this case, AWS
as an object storage cloud provider
and they have both native and non native.
The ability to, in essence, leverage object systems
that are native to AWS, in other words
AWS provide it, it's their tool, it only exists
on Amazon web services, no other cloud providers
And then non-native, we may use a particular
storage provider that exists on all of the clouds
and there's no reason we can't do that
you're just not necessarily leveraging something
that is optimized for that particular cloud
in some instances but sometimes it is
It doesn't really matter whether you leveraging
native or non native. It depends on the architectural
requirements of the business.