- [Instructor] So let's talk about the networking level
and the couple things that are important here.
Number one, some networking components
need to remain on-premises.
And so you have to remember, you need to understand
how networking exists in the cloud,
and even if we get into multi-cloud
or leveraging two or more public cloud providers
or dealing with hybrid cloud systems,
we're also linking private clouds or on-premise systems
with the public cloud.
Some of the components are going to need to remain on-premise,
and some of them are going to exist in the cloud.
So you as the architect need to figure out which ones.
Now, this doesn't mean
that you need to be a networking guru,
but this does mean that you need to understand
the basics of networking,
how things work, what resources exist in the cloud,
and what resources exist on-premises.
So the other types of networking can exist in the cloud,
but they're going to be different kinds of systems,
and so while we can have a DNS domain name service
that exists in the cloud, as well as on-premise,
there's different reasons to use a cloud-based version
versus an on-premise based version,
and you need to figure that out
as part of the architecture.
So as cloud architects,
we're looking at the network level this time,
and we have a couple of options there
that we can do in the cloud.
We have a DNS, domain name service.
We have IntraCloud,
the ability to communicate within the cloud,
and InterCloud.
And those are all fairly interesting things.
So the reason we would leverage a DNS
is because it's cheaper to do so in the cloud typically
than the on-premise systems,
and normally DNSs are typically things
that are hosted someplace.
Even if it's not in the cloud, it may be
at an Internet service provider's hosting facility.
IntraCloud typically is carried out by the cloud itself,
and it allows communications,
IPCs, interprocess communications,
and data communications, things like that,
but exists within the cloud.
Now, it's important that you understand how those work,
because you may have to set up different middleware systems,
data pipes, stream systems,
to allow these things to interact,
and you need to understand how they interact
and which are the best mechanisms to leverage.
And then finally, InterCloud,
which is fairly interesting
because it allows us to communicate with other clouds.
And so we may have to communicate with a private cloud,
such as a hybrid cloud architecture,
or more often then not,
we're communicating with other cloud brands,
such as AWS communicating with Microsoft,
communicating with Google,
or all three of them bound together.
And so you need to understand how that works.
So under DNS, we have different DNS servers
provided by cloud providers such as AWS and Microsoft.
And again, all have various good points and bad points.
You need to figure those out,
and why you would use their DNS
versus doing it on-premise
or even doing it on a cloud provider
versus doing it on an Internet service provider.
And then InterCloud,
we have the ability to have VPNs,
the ability virtual private network,
that exists between, say, our cloud and on-premise.
You know, such as AWS's Outpost,
which is their, kind of a pseudo-private
cloud version of AWS
that sits within data centers,
or VPC, virtual private clouds,
which allow us to, in essence,
leverage a private cloud in a public cloud,
as if the cloud was in our own data center,
which is interesting technology.