Skip to content

Commit 2d7ccee

Browse files
committed
Adding a video
1 parent 896fa9d commit 2d7ccee

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

articles/event-hubs/event-hubs-about.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,17 +27,19 @@ The following scenarios are some of the scenarios where you can use Event Hubs:
2727
- Archiving data
2828
- Transaction processing
2929
- User telemetry processing
30-
- Device telemetry streaming
30+
- Device telemetry streaming
31+
32+
[!VIDEO https://www.youtube.com/watch?v=45wgY-VSk9I]
3133

3234
## Why use Event Hubs?
3335

3436
Data is valuable only when there is an easy way to process and get timely insights from data sources. Event Hubs provides a distributed stream processing platform with low latency and seamless integration, with data and analytics services inside and outside Azure to build your complete big data pipeline.
3537

36-
Event Hubs represents the "front door" for an event pipeline, often called an *event ingestor* in solution architectures. An event ingestor is a component or service that sits between event publishers and event consumers to decouple the production of an event stream from the consumption of those events. Event Hubs provides a unified streaming platform with time retention buffer, decoupling event producers from event consumers.
38+
Event Hubs represents the "front door" for an event pipeline, often called an *event ingestor* in solution architectures. An event ingestor is a component or service that sits between event publishers and event consumers to decouple the production of an event stream from the consumption of those events. Event Hubs provides a unified streaming platform with time retention buffer, decoupling event producers from event consumers.
3739

38-
The following sections describe key features of the Azure Event Hubs service:
40+
The following sections describe key features of the Azure Event Hubs service:
3941

40-
## Fully managed PaaS
42+
## Fully managed PaaS
4143

4244
Event Hubs is a fully managed Platform-as-a-Service (PaaS) with little configuration or management overhead, so you focus on your business solutions. [Event Hubs for Apache Kafka ecosystems](event-hubs-for-kafka-ecosystem-overview.md) gives you the PaaS Kafka experience without having to manage, configure, or run your clusters.
4345

@@ -49,14 +51,14 @@ Ingest, buffer, store, and process your stream in real time to get actionable in
4951

5052
Azure Event Hubs also integrates with [Azure Functions](/azure/azure-functions/) for a serverless architecture.
5153

52-
## Scalable
54+
## Scalable
5355

54-
With Event Hubs, you can start with data streams in megabytes, and grow to gigabytes or terabytes. The [Auto-inflate](event-hubs-auto-inflate.md) feature is one of the many options available to scale the number of throughput units to meet your usage needs.
56+
With Event Hubs, you can start with data streams in megabytes, and grow to gigabytes or terabytes. The [Auto-inflate](event-hubs-auto-inflate.md) feature is one of the many options available to scale the number of throughput units to meet your usage needs.
5557

5658
## Rich ecosystem
5759

5860
[Event Hubs for Apache Kafka ecosystems](event-hubs-for-kafka-ecosystem-overview.md) enables [Apache Kafka (1.0 and later)](https://kafka.apache.org/) clients and applications to talk to Event Hubs. You do not need to set up, configure, and manage your own Kafka clusters.
59-
61+
6062
With a broad ecosystem available in various [languages (.NET, Java, Python, Go, Node.js)](https://github.com/Azure/azure-event-hubs), you can easily start processing your streams from Event Hubs. All supported client languages provide low-level integration. The ecosystem also provides you with seamless integration with Azure services like Azure Stream Analytics and Azure Functions and thus enables you to build serverless architectures.
6163

6264
## Key architecture components
@@ -75,7 +77,7 @@ The following figure shows the Event Hubs stream processing architecture:
7577

7678
## Next steps
7779

78-
To get started using Event Hubs, see the **Send and receive events** tutorials:
80+
To get started using Event Hubs, see the **Send and receive events** tutorials:
7981

8082
- [.NET Core](event-hubs-dotnet-standard-getstarted-send.md)
8183
- [.NET Framework](event-hubs-dotnet-framework-getstarted-send.md)

0 commit comments

Comments
 (0)