Azure Service Bus Flashcards
What is JMS 2.0?
JMS 2.0 (Java Message Service 2.0) is an updated API for messaging in Java that simplifies message-driven applications by introducing features like simplified API methods, asynchronous message consumption, and improved resource management. It enhances the efficiency of developing messaging-based Java applications.
What is AMQP 1.0?
AMQP 1.0 (Advanced Message Queuing Protocol) is an open standard messaging protocol designed for reliable, interoperable, and flexible message exchange across platforms. It ensures message delivery guarantees, supporting various patterns like publish-subscribe and point-to-point communication.
What is the default redundancy model?
The default resilience model for Azure Service Bus is region-based redundancy, meaning it offers high availability within a single region without zone redundancy. This provides reliability but may not protect against individual zone failures unless zone redundancy is explicitly enabled.
What is Azure Service Bus?
It is a platform-as-a-service Queue and pub-sub message broker
What are the SKU and Pricing tiers?
- Basic Tier:
Features:
Supports queues only; topics and subscriptions are not available.
Scheduled messages are supported.
Maximum message size is 256 KB.
Use Case: Suitable for simple, point-to-point messaging scenarios without the need for advanced features.
Pricing: Pay-as-you-go model based on the number of operations. - Standard Tier:
Features:
Supports both queues and topics with subscriptions.
Enables features like transactions, duplicate detection, sessions, and auto-forwarding.
Maximum message size remains at 256 KB.
Use Case: Ideal for applications requiring more advanced messaging patterns, such as publish/subscribe, with moderate throughput needs.
Pricing: Includes a base charge with additional costs per operation and brokered connections beyond the included quota. - Premium Tier:
Features:
Offers all features of the Standard tier with additional capabilities.
Provides resource isolation through dedicated resources, ensuring predictable performance.
Supports larger message sizes up to 100 MB.
Includes features like Geo-Disaster Recovery (Geo-DR), Virtual Network (VNet) integration, and Java Message Service (JMS) 2.0 support.
What type of messaging pattern does the Basic tier of Azure Service Bus support?
Point-to-point messaging (queues only)
Does the Basic tier of Azure Service Bus support topics and subscriptions?
No, only queues are supported.
What is the maximum message size in the Basic tier of Azure Service Bus?
256 KB
What is the best use case for the Basic tier of Azure Service Bus?
Simple point-to-point messaging scenarios without advanced features.
What additional messaging pattern does the Standard tier of Azure Service Bus support compared to the Basic tier?
Publish/subscribe (topics with subscriptions)
Which advanced features are available in the Standard tier of Azure Service Bus?
Transactions, duplicate detection, sessions, and auto-forwarding.
What is the maximum message size in the Standard tier of Azure Service Bus?
256 KB
What is the ideal use case for the Standard tier of Azure Service Bus?
Applications with moderate throughput requiring publish/subscribe messaging.
What resource allocation feature does the Premium tier of Azure Service Bus offer for performance?
Dedicated resources for predictable performance.
What is the maximum message size in the Premium tier of Azure Service Bus?
100 MB
Which additional advanced features are included in the Premium tier of Azure Service Bus?
Geo-Disaster Recovery (Geo-DR), VNet integration, and JMS 2.0 support.
What type of applications is the Premium tier of Azure Service Bus suited for?
Mission-critical applications requiring high throughput, low latency, and enhanced reliability.
Does the basic tier support Topics?
No, only queues
Does the basic tier support scheduled messages?
Yes scheduled messages are supported?
For the basic tier what is max message size?
256KB
What is the lowest cost tier where i can get Topic support
Standard Tier
What is a transaction?
In Azure Service Bus, a transaction is a feature that allows multiple operations to be grouped together into a single, atomic action. T
Explain Azure Service Bus Standard SKU?
$9.72 monthly per azure subscription
13million/operations free, 13-100M $0.80per M
Partial JMS 2.0 feature set
Shared environment
Explain Azure Service Bus Premium SKU?
Isolated environment
$0.928 per hour
Full JMS 2.0 feature set
What is a name space in Azure Service Bus?
In Azure Service Bus, a namespace is a container for all messaging components, which includes queues, topics, and subscriptions. It functions similarly to a “server” in other messaging technologies but is fully managed by Azure. Here’s a breakdown of what a namespace does:
Container: A namespace groups related Service Bus resources. Each namespace can contain multiple queues and topics, allowing you to logically organize your messaging entities.
Isolation: It provides isolation of resources, ensuring that queues, topics, and subscriptions within a namespace are accessible only within that namespace. This can enhance security and simplify access management.
Scalability: A namespace can be scaled to handle a large volume of messages. You can adjust throughput and other configurations at the namespace level to support high-demand scenarios.
Access Control: Access policies can be applied at the namespace level, giving fine-grained control over who can send, receive, or manage messages.
Each namespace is globally unique within Azure, meaning that it must have a unique name across all Azure subscriptions. When setting up Service Bus resources, you create a namespace as the first step before adding queues, topics, or any other messaging entities.
What option have we for integrating azure service bus in a vnet?
- Private Endpoint (Recommended for secure, private access)
Description: A Private Endpoint is a network interface that connects you privately and securely to Azure Service Bus via the Azure backbone network, with a private IP address from your VNet.
How It Works: With Private Endpoints, the Service Bus endpoint is accessible only within your VNet and connected VNets through a private IP address.
Advantages:
Blocks public access and allows only VNet-internal traffic.
Integrates with Azure DNS private zones to resolve the Service Bus namespace to its private IP.
Enhances security as traffic does not traverse the public internet.
- Service Endpoint (For additional access control)
Description: A Service Endpoint provides secure access to Azure Service Bus from a specific VNet subnet over the Azure backbone network.
How It Works: Service Endpoints extend the VNet’s identity to the Azure Service Bus service, allowing resources in that VNet to access Service Bus without needing public IP addresses.
Advantages:
Simplifies network security by allowing Azure Service Bus to recognize the subnet.
Can be configured with access control to limit access to specific subnets.
Limitations:
Unlike Private Endpoints, Service Endpoints do not block internet access to the Service Bus namespace.
Service Bus is still accessible over the public internet, so it’s less restrictive than Private Endpoints.
I have a Azure Service Bus with a Private Endpoint to a vnet, i want to restrict the network traffic to the ASB, what options do i have?
IP Firewall Rules (For allowing specific IP ranges)
Description: Azure Service Bus includes IP firewall rules that restrict access to specified IP addresses or IP ranges.
How It Works: Firewall rules allow you to control who can access your Service Bus namespace based on the IP addresses of incoming requests.
When using Azure Service Bus, do you get a public ip?
Azure Service Bus used to not provided a public IP, now it dose and you can turn it off if required or filter it using Azure Service Bus IP filters, you also get a FQDN and Premium tier supports VNet service endpoints and private endpoints for enhanced security.
Can i use the standard SKU with vNET private or service endpoints?
No, VNet service and private endpoints are only available with the Premium SKU of Azure Service Bus, not the Standard SKU.
Can you create a hierarchical name space for your Azure Service Bus?
Yes in the name space you can create hierarchical name space.
For Azure service bus what is the max message sizes for each sku?
Basic :
Messages can be up to 256 KB in size.
Standard :
HTTP and SBMP Protocols: Limited to 1 MB per message.
Premium Tier:
HTTP and SBMP Protocols: Limited to 1 MB per message.
AMQP Protocol: Supports messages up to 100 MB.
You can use paretations and get upto 80GB
When a message is accepted by Azure Service Bus, how is it copied?
Triple replicated to disk.
How do you push a message in the dead letter queue?
You call the dead letter api (same api just the dead letter part)
Why would you call the dead letter queue?
You (consumer) can handler it or there is a continued error)
What is scheduling in Azure Service Bus?
Scheduling in Azure Service Bus allows messages to be sent at a future time, enabling delayed message delivery. This feature is useful for scenarios where messages need to be deferred for processing later. Scheduled messages are held in the queue or topic until their delivery time.
Is scheduling in Azure Service Bus available on basic and standard tier
Yes, Azure Service Bus supports scheduled messages in both the Basic and Standard tiers. This feature allows you to send messages that are delivered at a specified future time, enabling delayed processing scenarios.
AZURE
Can you cancel Azure Service Bus scheduled messages?
Yes
What is a deferral in Azure Service Bus ?
A deferral in Azure Service Bus allows a message to be set aside temporarily when a receiver cannot process it immediately. The message remains in the queue but is hidden from other receivers. The deferred message can be retrieved later using its unique sequence number for processing.
What is a session in Azure Service Bus?
In Azure Service Bus, a session groups related messages with the same SessionId, enabling ordered, stateful message processing by a single receiver. This feature is useful for scenarios where message order and context are critical. Only one client processes each session at a time, ensuring exclusive handling.
What can you do for a queue that is super quite and what to save resources?
You can intergrade Azure Service Bus with Event Grid and subscribe for “ActiveMessageWitNoListeners”, this kicks off Azure Event Grid and Event Grid can be used to spin up consumer to deal with the message.
What is a transaction in Azure Service Bus ?
its where the entire transaction suiceeds of not, this will meant that a consumer receives a message and is about to do some work by sending further messages, all messages need to succeed or all message will fail as a group.
What is the primary purpose of Azure Service Bus?
To provide a reliable messaging service between applications and services.
What is a Service Bus Topic?
A messaging entity that allows multiple subscribers to receive copies of messages.
How does Service Bus ensure message delivery?
It uses a queuing mechanism to guarantee at-least-once delivery of messages.
What are the key use cases of Azure Service Bus?
Asynchronous messaging, decoupling of services, and load leveling.
What are the key features of Service Bus Topics?
Message filtering, multiple subscriptions, and session support.