Develop Message-based Solutions Flashcards
Azure Queue Storage
High level, what would a message based architecture look like?
(1) User Sends Order
(2) Message received by Order Queue
(3) Order Fullfillment Service recevies messages and processes
(4) Message send to Post-Order Queue
(5) Analytics Ingestion Service
Azure Storage Queue
Benefits of a message-based architecture
(1) Encourages application logic modularity
(2) Enables fault tolerance between modules
(reduces data loss)
Azure Storage Queue
Define the Azure Storage Queue
A fully-managed service that is a part of the Azure Storage suite that enables you to create durable and configurable message queues to enable application modularity and fault tolerance
Azure Storage Queues
What are the capabilities of the Azure Storage Queue?
(1) Requires an Azure Storage Account
(general purpose v2)
(2) Queues are created within a single storage account
(3) Supports messages up to 64 KiB in size
(4) Number of messages limited only by size of the storage account
(5) Supports a configurable time-to-live per message
(default is 7 days)
Azure Storage Queues *
What are the data redundancies?
(1) Locally Redundant Storage (LRS)
(2) Zone-Redundant Storage (ZRS)
(3) Geo-Redundant Storage (GRS)
(4) Geo-Zone Redundant Storage (GZRS)
(5) Read-Access Geo-Redundant Storage (RA-GRS)
(6) Read-Access Geo-Zone-Redundant Access (RA-GZRS)
Zone means data is stored in more than one data center within a zone
Azure Storage Queues
Security Features in Azure Storage Queues
(1) Data in queues is encrypted by default
(2) Azure Storage stored access policies can work with queues
(3) Interactions with queue data via HTTP or HTTPS
(4) Supports the following authorization approaches
(a) Shared Key
(b) Shared Access Signature
(c) Azure AD
Azure Storage Queues
What is the Visibility Timeout?
Messages are delivered to consumers, butr are not immediately deleted from the queue. However, messages will not be visibile in the queue until a period of time has passed from the initial delivery.
Messages delivered to the consumer are not immediately deleted from the queue.
Azure Storage Queues
Scalability (queue, message, message support)
(1) Single queue < 500 TiB
(2) Single message cannot exceed 64 KiB
(3) No more than 5 access policies
(4) A storage account can support up to 20,000 messages per second
(based on 1 KiB message size)
(5) A single queue can support 2000 messages per second
(based on 1 KiB message size)
Azure Storage Queue
How to Create, Delete, View, Delete all messages a Storage Queue using Azure CLI
Create a Queue
az storage queue create –name $myqueue
Delete a Queue
az storage queue delete –name $myqueue
**View Messages **
az storage message peek –queue-name $myqueue
Delete All
az storage message clear –queue-name $myqueue
Azure Service Bus
Definition of Azure Service Bus
Full managed enterprise message broker service that enables multiple modes of messaging with integrations for common messing systems including Java Message Service (JMS)
Types of Azure Service Bus Messaging
(1) queue
(2) Topics
Azure Service Bus
Features of Azure Service Bus
(1) Supports both HTTP/HTTPS and AMQP protocols
(2) Includes messaging for both queues and topics
(3) Supports 3 different tiers
(basic, standard, and premium)
(4) Supports advanced Configurability
(Ordering, Batching, DLQ or Dead-letter queue, and duplication detection)
Basic tier DOES NOT support Topics
Azure Service Bus
What are some key differences between Standard and Premium Tiers for Azure Service Bus?
(1) Pay as you go vs. Fixed based on messaging units
(2) Throughput is varialble vs Throughput is fixed based on messaging units
(3) Shared vs dedicated resources
(4) Auto scaling vs configuration of scaling
(5) 256 kb vs 1 mb messages
(6) No support for geo-disaster recovery or availability zones
Azure Service Bus
URL Makeup
Azure Service Bus
Message Ordering
Azure Service Bus supports FIFO ordering by leverage sessions. This is supported in queue and topcis but must be enabled on the queue or topic