#GlobalAzureGreece

#GlobalAzure
 Intro to Azure Service Bus

An introduction to Azure Service Bus with a short demo

combining Service Bus Queues and Azure Logic Apps.

George - Chrysovalantis Grammatikos

MCSA : Cloud Platform, MS Dynamics 365 | Microsoft Azure MVP

E-mail : george@cloudopszone.com
Blog: https://cloudopszone.com
Microsoft Community Wiki Profile: George Chrysovaladis Grammatikos
Tech Community Profile: George Chrysovalantis Grammatikos
 Azure Messaging Services

Service Bus Event Grid Event Hub Storage Queue Azure Relay

 P2P messaging  HTTP-based event  Simple (Few clicks to  Basic P2P  Securely Expose on-
 Pub-Sub messaging delivery build real data Communication premises services
 Cost efficient  Supported by many pipelines)  Cost Effective (pay only Relay
 Durable brokered azure services  Secure (Certified by for what we use)  Shared access
messaging  Near real-time CSA STAR, ISO, PCI,  Compliance signature(SAS)
 Ent. messaging notifications HIPAA, HITRUST, GxP) certifications (ISO, authentication
functionality  First 100.000  Massively scalable ITAR, CSA, CDSA)
 Sessions operations are free  Open (Support
 Duplicate
popular protocols,
Detection
AMQP, HTTPS, Apache
 Message
Kafka.)
Expiration
 Scheduled
Expiration
 Messaging in real life

Healthcare Financial Logistics

Telecommunications Public Sector

 Azure Service Bus
Azure Service Bus (Messaging as a Service - MaaS) is an asynchronous cloud delivery messaging service,
and offers a secure data transfer between different applications.

Namespace Protocols

HTTP-HTTPS
Queues Topics AMQP SBMP
Service Bus
Messaging Protocol

 Cross platform
 Default protocol used  Default protocol used compatibility with
This is a publish-subscribe model, by Service Bus SDK by Service Bus SDK many clients
Many Front End applications send
push the message into a topic and  Supported by many  Supported by many  Provide
messages to the queue and one
that message sent to all subscribers apps apps communication
application on the back end serves
one to many, e.g Twitter or Facebook  Open messaging  Open messaging where firewalls may
those requests in order of priority,
feeds. protocol protocol limit connectivity on
 Ports 5671 & 5672  Ports 930 & 9354 other protocols.
 Ports 80 & 443
 Enterprise Service Bus
“An enterprise service bus (ESB) implements a communication system between mutually interacting
software applications in a service-oriented architecture (SOA). It represents a software architecture for
distributed computing, and is a special variant of the more general client-server model, wherein any
application may behave as server or client.”

Source: wikipedia

Enterprise Service Bus (ESB)

 Azure Service Bus Queue

Message Sender Service Bus Message Receiver

Namespace

Web App
Service or App
Mobile App Queue

Service App

 P2P messaging
 First In, First Out (FIFO) processing
 Azure Service Bus Topics & Subscriptions

Message Sender Service Bus Message Receiver

Namespace

Web App
Subscription
01 Service or App 01

Mobile App Topic

Subscription
02
Service or App 02

Subscription Service or App 03

Service App 03

 Pub – Sub messaging

 Messages are sent to Topics and received from Subscriptions
Azure Service Bus Pricing Tiers
 Azure Service Bus Features Per Tier
Feature BASIC TIER STANDARD TIER PREMIUM TIER
Queues Available Available Available
Scheduled messages Available Available Available
Topics Not available Available Available
Transactions Not available Available Available
De-duplication Not available Available Available
Sessions Not available Available Available
Forward TO / Send Via Not available Available Available
Message size 256 KB 256 KB 1 MB
Brokered connections included 100 10,001 1,000 per MU
Brokered connections (overage allowed) Not available Billable Up to 1,000 per MU
Resource isolation Not available Available
Geo-disaster recovery (Geo-DR) Not available Available (Requires additional Service
Bus Premium namespaces in another
region)
 Azure Service Bus Advanced Features

Feature Description

Message sessions Sessions are grouped related messages and processed together, also
sessions can guarantee FIFO sorting
Duplicate detection Duplicate messages can be ignored by a messaging entity

Message deferral Messages can be preserved on a messaging entity and retrieved later
for processing
Dead-lettering Invalid or poison messages can be moved to a dead-letter queue

Message expiration Messages can be configured to expire after a specified duration

Batching Messages can be sent in a single batch, during a period of time delay
on a queue or a topic
Scheduled delivery Messages can be start processing at a certain time after a delay.

Auto-forwarding Automatically removes a queue or subscription to another queue or

topic in the same namespace.
Filtering and actions The subscriber can filter which message want to receive from the
topic.
 Service Bus Tools

1. Azure Portal

2. Visual Studio

3. Visual Studio Code

4. Service Bus Explorer

 To keep in the mind…

 Think what do you want to do before decide what is the appropriate Service Bus .Net SDK

 It is a wise option to select AMQP protocol

 Use concurrent operations

 Use multiple queues/Topics

 Azure Service Bus .Net SDK

The old…. The new….

WindowsAzure.ServiceBus Microsoft.Azure.ServiceBus

• AMQP, HTTP
• AMQP, SBMP, HTTP
• .Net Core 2.0, .Net Framework 4.6.1, Mono 5.4, Xamarin.iOS 1014, Xamarin.Mac 3.8,
• .Net Framework 4.6.1
Xamarin.Android 8.0, Universal Windows Platform 10.0.16299
• Primary Namespaces:
• Primary Namespaces:
• Microsoft.ServiceBus
• Microsoft.Azure.ServiceBus
• Microsoft.ServiceBus.Messaging
• Microsoft.Azure.ServiceBus.Management
 Concurrent operations
Usually operations like send, receive, or delete, takes time. To reduce this latency it is best practice to use
Concurrent operations, because with that way we can increase the number of operations.

Microsoft.Azure.ServiceBus SDK WindowsAzure.ServiceBus SDK

var messageOne = new Message(body); var messageOne = new BrokeredMessage(body);
var messageTwo = new Message(body); var messageTwo = new BrokeredMessage(body);

var sendFirstMessageTask = var sendFirstMessageTask =

queueClient.SendAsync(messageOne).ContinueWith(_ => queueClient.SendAsync(messageOne).ContinueWith(_ =>
{ {
Console.WriteLine("Sent message #1"); Console.WriteLine("Sent message #1");
}); });
var sendSecondMessageTask = var sendSecondMessageTask =
queueClient.SendAsync(messageTwo).ContinueWith(_ => queueClient.SendAsync(messageTwo).ContinueWith(_ =>
{ {
Console.WriteLine("Sent message #2"); Console.WriteLine("Sent message #2");
}); });

await Task.WhenAll(sendFirstMessageTask, sendSecondMessageTask); await Task.WhenAll(sendFirstMessageTask, sendSecondMessageTask);

Console.WriteLine("All messages sent"); Console.WriteLine("All messages sent");
 Multiple queues/Topics
If we cannot predict the application load we can use multiple messaging entities,
More than one queues or topics.

Order Processing
Restaurant
01

Hotel Web Topic Order Processing

Bar
App {Orders} 02
Spa / Order Processing
Hammam 03
Demo
Thank You
Coming next…

Building low code/no code

services with Azure