10. Apps Integration Services
Azure Queue Storage
A place for messages to be stored before something picks it up to use. Simpler than Service Bus, not recommended for critical information.
Publisher and Receiver - send and receive messages (XML, JSON, Text, etc) via REST Storage Account Queue - endpoint for messages to be published to and recieved - (poll/pull)
Azure Service Bus
Enterprise scale messaging service. Used when you want to guarantee a delivery correctly, not duplicated, not out of order. Topics can be used to enhance functionality.
- FIFO, at most once, at least once guarantees
- supports sessions, dead lettering, duplicate detection and more
- maximum message size of 256kb/100mb, 10,000 queues.
Pricing
Basic Standard - shared capacity - max 256kb message, queues and topics Premium - dedicated - max 1mb message, all of the above plus zone redundancy.
Resources
Publisher and Receiver - send and receive messages (XML, JSON, Text, etc) via REST Namespace - container for service bus Queue - FIFO delivery queue
Topics
Endpoint for message publishing
- supports ordering, partitioning, etc
Subscription - messages that are duplicated from a topic can go into these different subscriptions.
Event Grid
This is about events, not messages. Can include IoT devices
- basic service provides lightweight delivery of events
Basic
- publisher subscriber push model
Standard
- IoT, MQTT support, pull model
Event Grid Topics
Event Publisher
Event Handler
Event Grid service
Topics - collection of related published events
Event Hubs
Streams of event data
- near realtime
- Supports AMQP, HTTPS, Apache Kafka and more
Components
Event Hub Namespace Event Hub Partition Consumer group - a view of the hub to see where your events are.
Azure API Management
- API documentation
- Access to the APIs via API Gateway
Basic v2 - dev test Standard v2 - production, development portal
Management plane Rate limits and quotas, security validation. caching, transformations and self hosted options.
No more v1 :(
Azure Logic Apps
Trigger - time based Does something GUI based workflows with connectors for various services
Components
Logic App Resource Workflow (can save as JSON) Triggers and Actions Connectors
Pricing Models
Consumption
Standard
Case Study
https://learn.cantrill.io/courses/az-305-microsoft-azure-solutions-architect/lectures/48733866
- All APIs are exposed to the Internet
- no caching on the APIs
- slower responses to negative reviews
- handled on manual basis
Solution:
- Turn off backend public access using APIM Standard v2
- Logic App for feedback to create a SN ticket