Whether we're talking about children
or full grown adults, no one enjoys
having their stuff messed with.
In this lesson, we are going to talk about
how to handle interruptions in Azure Stream Analytics.
And this may be one of the shortest lessons
that I have done to date.
In this lesson, we're going to be discussing paired regions.
Yes, no, that's it. Just paired regions, so pretty fast.
With that, let's go ahead and just jump in
and start talking about it.
Before we talk about paired regions,
we first have to start talking about availability sets.
So an availability set is just a separation of your data
in separate hardware within a datacenter.
So think 2 different computers
both storing your data within the same datacenter.
So this is going to give you some protection
if one machine fails, okay?
It's not going to protect you
if the datacenter fails, though.
If that's the case, you got to look at an availability zone.
So think about Chicago having 2 different datacenters.
Both of those datacenters are storing your data
and they both have multiple copies of your data
within those availability sets.
However, we still have a problem
because what if a tornado comes and just wipes out Chicago?
Well, if that's your concern,
then we need to look at regions.
And when we talk about regions,
now what we're talking about is the separation of location.
So I can have a datacenter in Chicago
and then I can have a datacenter in New York
and that would be a region pair
of East U.S. and Central U.S.
So I have 2 different datacenters
in 2 different regions.
So now I have separation of the region,
I have separation of the datacenter,
and I have separation of the data within the datacenter
with those availability sets.
Now, I mentioned that pair.
So regions pair together
and Azure has 2 different regions that pair together.
So for instance, like I said, you can have a Central U.S.
and an East U.S. or you can have
an East U.S. and a West U.S.
And so you choose a pair.
And then within that,
that is going to be within the much larger geography.
So U.S., that would be your geography.
And so when we look at building protection,
Azure recommends that if you have mission-critical jobs
that you need to create an availability on a paired region.
So, basically, what you're doing is you are going to look
at a region pair, like Central and East U.S.,
and then what you're going to do is
you are going to run identical jobs
in both of those paired regions.
That way, if something happens,
you have some protection in case of a critical failure.
Now, of course, Microsoft's going to work very hard
to avoid having a failure.
But if you have something that is mission critical,
Microsoft is recommending
that you use an Azure paired region.
So with that, let's talk about the review.
So first, the Stream Analytics guarantee.
So Microsoft promises that when they do updates,
they will update in separate batches for paired regions.
That means that East U.S. and West U.S.
are not going to be updated at the same time.
They're going to update one and then update the other.
So with that, the deployment of the updates
don't occur at the same time.
So because of that, make sure that if you need
to run a mission-critical stream analytics job
that you're going to deploy that
to 2 different paired regions at the same time.
If you do that, you're going to be well-protected
against any mayhem that might occur.
So with that, that's it, we're done.
We're ready to move on to the next lesson.
Just make sure you keep that
Stream Analytics guarantee in mind.