Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Azure for Architects

You're reading from   Azure for Architects Implementing cloud design, DevOps, containers, IoT, and serverless solutions on your public cloud

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781789614503
Length 536 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Ritesh Modi Ritesh Modi
Author Profile Icon Ritesh Modi
Ritesh Modi
Daniel Andres Pelaez Lopez Daniel Andres Pelaez Lopez
Author Profile Icon Daniel Andres Pelaez Lopez
Daniel Andres Pelaez Lopez
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Getting Started 2. Azure Solution Availability and Scalability FREE CHAPTER 3. Security and Monitoring 4. Cross-Subscription Deployments Using ARM Templates 5. ARM Templates - Modular Design and Implementation 6. Designing and Implementing Serverless Solutions 7. Azure Integration Solutions 8. Cost Management 9. Designing Policies, Locks, and Tags 10. Azure Solutions Using Azure Container Services 11. Azure DevOps 12. Azure OLTP Solutions Using Azure SQL Sharding, Pools, and Hybrid 13. Azure Big Data Solutions Using Azure Data Lake Storage and Data Factory 14. Azure Stream Analytics and Event Hubs 15. Designing IoT Solutions 16. Other Books You May Enjoy

Architecture of Event Hubs

There are three main components of the Event Hubs architecture: the Event Producers, the Event Hub, and the Event Consumer, as shown in the following diagram:

Event Producers generate events and send them to the Event Hub. The Event Hub stores the ingested events and provides that data to the Event Consumer. The Event Consumer is whatever is interested in those events, and they connect to the Event Hub to fetch the data.

Event hubs cannot be created without an Event Hubs namespace. The Event Hubs namespace acts as a container and can host multiple event hubs. Each Event Hubs namespace provides a unique REST-based endpoint that is consumed by clients to send data to Event Hubs. This namespace is the same namespace as is needed for Service Bus artifacts, such as topics and queues.

The connection string of an Event Hubs namespace is composed of its URL...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime