- [Narrator] So let's continue with our example.
So what's important here
is that you have to understand how we get different Clouds
working and playing well together.
So, at the end of the day,
this is not just you standing up one instance
of a Cloud architecture on one instance of a Cloud;
this is about a true architecture.
Your ability to get things working and playing well together
on premise, in the public Cloud, in the private Cloud,
IOT based systems, Edge based systems,
whatever we're evolving to.
So, MulitClouds are most of the Cloud architecture
that you see out there.
So, it's never going to be just Amazon web services
or just Microsoft, it's going to be a mixture
of Amazon, Microsoft, Google,
could be a mixture of just Amazon and Microsoft,
it could be Google and Microsoft,
and it could be a number of proprietary Clouds
or special purpose Clouds that are built
so, each architecture is going to be very different.
And one of the things you need to understand
if you're going to be a Cloud computing architect,
is the fact of the matter is that
these very complex things shouldn't scare you.
Ultimately, it's about breaking them down
into their functional primitives, the core solutions,
and then building them back up,
with the requirements that you understand about the business
to be something better.
Leveraging the Cloud.
So, back to our fictional company,
Industrial Drones International,
we have the inventory control systems
and we then have a SaaS, Software as a Service, Cloud,
Which is their Enterprise Accounting system,
so, Amazon Linux, App Server Instance and Amazon Aurora,
which is the way we went, and basically,
this is going to be our inventory control system.
Migrated to the Cloud.
So, we're able to interact, in this case,
with the Software as a Service system,
our Enterprise Accounting system,
via APIs that this particular Software as a Service system
is exposing to systems that are outside of its Cloud.
And so, in other words, directly from Amazon
we're able to invoke APIs,
that we're able to do through public API gateways,
which allow us to pull information, to pull behaviors,
from these other Cloud based systems, in this case,
a Software as a Service Cloud.
It could be Salesforce, it could be QuickBooks,
it can be any number of systems out there.
And so the idea here,
is really to depict the functionality
of the fact that we're going to be make these systems
work and play well together because we have
the common mechanism of APIs,
Application Programing Interfaces,
that allow us to invoke services,
and pull information from within Amazon,
or invoke services and pull information
within this particular fictitious platform
as a service provider.
And so, it could be Microsoft, it could be Google,
in terms of an infrastructure as a service player,
which can interact using the same sorts of APIs,
as Salesforce.com, as QuickBooks, NetSuite,
the typical SaaS companies that we're dealing with
out there within the enterprise.