Azure Service Bus

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
14 hours 28 minutes
Difficulty
Intermediate
CEU/CPE
15
Video Transcription
00:00
>> Hello Cybrarians.
00:00
Welcome to Lesson 7.2 of Module 7 of this course title;
00:00
AZ-301: Microsoft Azure Architect Design.
00:00
Here are the learning objectives for this video.
00:00
We'll start out by introducing you
00:00
>> to Azure Service Bus.
00:00
>> Then we'll cover some useful information on how
00:00
exactly this service works
00:00
>> and how it does what it does.
00:00
>> We'll then cover the different SKUs
00:00
that are available if we want to implement
00:00
Azure Service Bus so that we're able to
00:00
select the right option for our architecture.
00:00
We'll cover the differences between
00:00
Azure Queue storage and Service Bus.
00:00
Let's get right into this.
00:00
Let's talk about Azure Service Bus.
00:00
According to Microsoft Azure Service Bus is
00:00
a fully managed enterprise integration message broker.
00:00
Service Bus is most commonly used to decouple
00:00
applications and services from each other,
00:00
and it's a reliable and secure platform
00:00
for asynchronous data and state transfer.
00:00
What does this mean?
00:00
What this means is when we're moving away,
00:00
or when we start to move away from
00:00
the monolithic approach to application development,
00:00
to microservices approach
00:00
and application development where
00:00
we're breaking down our application
00:00
into different logic component.
00:00
We have to get all these different logic components
00:00
to communicate between one another.
00:00
One of the ways to implement
00:00
that communication is to use queuing or to use queues.
00:00
Azure Service Bus, and it's
00:00
a message broker service which
00:00
allows us to be able to implement queues and topics,
00:00
to be able to pass messages between
00:00
different services or
00:00
different components of the same service,
00:00
or of the same application, or even of
00:00
disparate services are disparate applications.
00:00
How does Azure Service Bus work?
00:00
When we want to start working with Azure Service Bus,
00:00
the first thing we need to do is to create
00:00
something called a Service Bus name-space.
00:00
A Service Bus namespace is the container for everything
00:00
else that we will be working with in Service Bus.
00:00
The message in components that queues the topics,
00:00
all of that lives within a Service Bus namespace.
00:00
After we have a Service Bus namespace,
00:00
then we'll create our queues,
00:00
and we create our topics.
00:00
Now, both queues and topics have
00:00
similar purposes to store messages received from
00:00
a sender until the receiving application
00:00
is available to receive and process those messages.
00:00
That's the purpose of queues and topics.
00:00
In terms of they differ from one another,
00:00
a queue is often used for point-to-point communication.
00:00
In other words, you have one sender passing the message
00:00
into a queue to be collected by one receiver.
00:00
On the other hand,
00:00
a topic is useful in publish-subscribe
00:00
scenarios where you have
00:00
one sender with multiple receivers.
00:00
What a topic allows us to do is to have
00:00
this different streams that
00:00
different receivers can consume
00:00
so that the message is split out
00:00
all these different streams and
00:00
each receiver can consume that at its own pace.
00:00
Azure Service Bus, like
00:00
other services that we've talked about in this module,
00:00
have native integrations built-in
00:00
to other Azure services.
00:00
For example, it has native integration built-in with
00:00
Azure Event Grid with Azure Logic Apps.
00:00
For example, we could use message that's
00:00
received in a queue to pass an event into Event Grid,
00:00
or we could do the same thing to trigger
00:00
a logic app execution, for example.
00:00
We can use messages as put into a Service Bus queue or
00:00
a topic to trigger an Azure function to execute,
00:00
or we can do it the other way
00:00
around where Azure function,
00:00
after it finishes execution,
00:00
it's going to put a message in
00:00
a queue which can be picked
00:00
up by maybe by another Azure function
00:00
or by another service.
00:00
It has integration with Dynamics 365,
00:00
it has integration with Azure Stream Analytics,
00:00
where we could stream all these different messages
00:00
and then perform more advanced analytics on them.
00:00
Types of Service Bus queues,
00:00
they're three main SKUs that are available.
00:00
We have the basic,
00:00
the standard and premium SKUs.
00:00
When we create a Service Bus namespace,
00:00
we have to specify the SKU that we want.
00:00
The SKU that we select that means
00:00
the features that are available for us to use.
00:00
If you look at basic on the left-hand side,
00:00
you notice that topics and subscriptions and not
00:00
supported in the basic pricing tier, it's only queues.
00:00
That's just point-to-point communication,
00:00
not the publish-subscribe model.
00:00
The standard SKUs support topics and support queues,
00:00
one of the main capabilities that premium has,
00:00
which is not shown on the screen,
00:00
but it supports geo redundancy.
00:00
It does support that.
00:00
If you have the premium [inaudible],
00:00
it provide resource isolation at the CPU and
00:00
memory level so that each workload runs in isolation.
00:00
It has that dedicated capacity,
00:00
it's not using shared capacity.
00:00
You can see that the pricing model is also different.
00:00
With the standard you're
00:00
paying per message in operation,
00:00
whereas with the premium once you've paid for that,
00:00
it covers all the
00:00
messaging operations that you'll be doing.
00:00
Let's talk about this comparison that comes up
00:00
between Azure Queue Storage and Service Bus.
00:00
Now, one of the sub services
00:00
on the Azure storage account
00:00
is something called Azure Queue.
00:00
It also supports queuing where we can
00:00
put messages into a queue but
00:00
there's differences between what
00:00
that support versus what Service Bus support.
00:00
In essence, the difference is about
00:00
enterprise functionality versus queues.
00:00
Enterprise functionality on the side of Service Bus
00:00
or more advanced functionalities
00:00
on the side of Service Bus.
00:00
Not that Azure Queue storage is not enough,
00:00
it's on advanced functionality,
00:00
it does in some cases have
00:00
some functionality that advanced
00:00
Service Bus doesn't have but in most cases
00:00
Service Bus has they advanced functionalities,
00:00
while Azure storage queue as the SKU, the massive SKU.
00:00
For example, if you have a look on the screen,
00:00
you can see things like ordering guarantee,
00:00
Service Bus supports first-in-first-out while
00:00
Storage Queues doesn't provide
00:00
any ordering guarantee in other words
00:00
our message is going to be
00:00
hoarded in terms of the guarantee.
00:00
About delivery guarantee,
00:00
storage queue supports only the at-least-once model
00:00
while Service Bus queue
00:00
support at least once and at most once.
00:00
You can see the comparison on the screen,
00:00
I won't go through every single thing.
00:00
When it comes to what's on
00:00
the side of Azure Queue storage, you can see the scale.
00:00
For example, if you have a look
00:00
at the size of the queue,
00:00
for Service Bus queue,
00:00
the maximum size can go up to 80 gigabyte.
00:00
For storage queue,
00:00
that could go up to 500 terabytes,
00:00
and actually that can go up
00:00
to the size of the storage account.
00:00
In some Azure regions,
00:00
the maximum size of a storage account is two petabytes.
00:00
That's very large queue that you're talking about.
00:00
But you can also see in terms of
00:00
the message sizes that they support.
00:00
Where Azure Service Bus supports message sizes
00:00
of 256 kilobytes or one megabyte.
00:00
This brings me to the end of this lesson.
00:00
Thanks very much for watching,
00:00
and I'll see you in the next lesson.
Up Next