Scribd
Upload
57 views21 pages

Azure 305 Appdesign - Participat

Uploaded by

majbah00
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
57 views21 pages

Azure 305 Appdesign - Participat

Uploaded by

majbah00
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 21

AZ-305T00A

Designing Microsoft
Azure Infrastructure
Solutions
Introduction

• Describe message and event scenarios


AZ-305: Design infrastructure solutions (25-30%)
• Design a messaging solution Design an Application Architecture
• Design an event solution (Event Hub and  Recommend a caching solution for applications
Event Grid)  Recommend a messaging architecture
• Design an application optimization  Recommend an event-driven architecture
solution  Recommend an automated deployment solution
for your applications
• Design application lifecycle  Recommend an application configuration
• Case study management solution
 Recommend a solution for API integration
• Summary and resources
Describe message and event scenarios
Determine message and event scenarios
Does the sending component expect the communication to be processed in a specific way?

Action Description When to use

Event • Light weight Used for broadcasts and are often


• Includes a publisher and a subscriber ephemeral. Ephemeral means the
communication might not be handled
by any receiver if none is currently
subscribing.

Message • Contains raw data, produced by one Used where the distributed application
component, that will be consumed requires a guarantee that the
by another component. communication will be processed.
• Contains the data itself, not just a
reference to that data.
Design a messaging solution
Design for Azure Queue storage
Azure Storage Queue is a service for storing large number of messages.

• Accessed with authenticated calls using


HTTP or HTTPS
• Messages can be up to 64 KB in size
• May contain millions of messages, up to
the total capacity limit of a storage
account • Create a backlog of work to process asynchronously
• Example: customer placing orders online added to
the queue and processed
Design for Service Bus queues and topics
Service Bus decouples applications and services from each other.

Service bus queues Service bus publish-subscribe topics

• Built on top of a dedicated messaging • Like bus queues but with multiple subscribers
infrastructure
• When a message is sent to a topic, multiple
• Holds messages until the target is ready to components can be triggered to perform a
receive them – different from queues task
Compare messaging solutions
Solution Usage cases SLA
Queue • A simple queue to organize messages. Based on
storage • Queue to exceed 80 GB in size. storage tier
• To track progress for processing a message inside of the queue.
• Maximum message TTL of 7 days
Service bus • A first-in-first-out guarantee. 99.9%
queues • An at-most-once delivery guarantee.
• Can group messages into transactions.
• Receive messages without polling the queue.
• Provide a role-based access model to the queues.
• Publish and consume batches of messages.
Service bus • Multiple receivers to handle each message. 99.9%
topics • Multiple destinations for a single message.
Design an event solution
Design an Event Hub messaging solution
Azure Event Hubs is a fully managed, real time data ingestion service

• Orders events by when they are


received - by time offsets
• Uses a pull model allowing
multiple reads from consumers
• Scaling is controlled by how
many throughput units or
processing units you purchase
• Doesn’t account for messages
that aren't processed
• Receiving IoT and real-time
streaming data
Design an event-driven solution
Azure Event Grid is a routing service connecting data sources with event handlers.

• Events sources include Azure


resources or custom topics (you
create)
• Event handlers react to an event
• Useful for serverless applications and
operations automation
• Use filters to route and multicast
events
• Uses a pay-per-event pricing model
Comparison of message and event solutions
Consider combining several solutions

Service Purpose Type When to use

Event Grid Reactive programming Event distribution (discrete) React to status changes

Event Hubs Big data pipeline Event streaming (series) Telemetry and distributed data
streaming

Service Bus High-value enterprise Message Order processing and financial


messaging transactions
Design an IoT Hub solution
Central message hub for IoT applications and its attached devices.

When to use IoT Hub?


• Application complexity
• Data throughput
• Securing solution end to end
allowing for per-device
authentication
• Bi-directional communication
Capabilities over Event Hub:
• Per-device identity
• File upload from devices
• Device provisioning service
Design an application optimization solution
When to use Azure Cache for Redis
Store frequently accessed data so that applications can be responsive to users.

• Key scenarios - data cache, content cache,


session store, job and message queuing, and
distributed transactions
• Fully managed solution
• High availability - responds automatically to
both anticipated and unanticipated changes in
demand
• Same performance and scaling benefits
throughout the world – network isolation,
data encryption in transit
Design an Azure API management solution
Publish, secure, maintain, and analyze all your company's APIs.

• Bring multiple APIs under a single


administrative umbrella – centralized
management
• Manage permissions and access
• Ensure compliance across API
• Standardize API specs
• Protect the APIs from malicious usage
Design an application lifecycle
What is Infrastructure as Code?
Infrastructure as Code (IaC) is the process of automating your infrastructure provisioning.

• The IaC model generates the same


environment every time it is applied
• Solves the problem of environmental
drift
• Enables teams to test applications in
production-like environments early
• Where possible, uses declarative
definition files
Provision resources with Infrastructure as Code
Azure supports IaC with Azure Resource Manager and third-party platforms.

• Azure Resource Manager templates –


Bicep, JSON
• Azure Automation
• Azure DevOps services
• GitHub actions
• Terraform
• Jenkins
Summary and resources

Check your knowledge Microsoft Learn Modules (docs.microsoft.com/Learn)

Choose a messaging model in Azure to loosely connect your services

Introduction to Azure API Management

Introduction to Event Hubs


Deploy Azure infrastructure by using JSON ARM templates

Introduction to infrastructure as code using Bicep

Message queues and stream processing

Introduction to Azure Cache for Redis

Optional hands-on exercise - Implement a Service Bus topic and queue - Learn | Microsoft Docs
End of presentation

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy