专用事件中心概述Overview of Event Hubs Dedicated

事件中心群集提供单租户部署来满足客户的苛刻流式处理要求。Event Hubs clusters offer single-tenant deployments for customers with the most demanding streaming needs. 此单租户套餐提供有保障的 99.99% SLA,只能在专用定价层上使用。This single-tenant offering has a guaranteed 99.99% SLA and is available only on our Dedicated pricing tier. 事件中心群集每秒能够引入数百万个事件,且提供有保障的容量和亚秒级的延迟。An Event Hubs cluster can ingress millions of events per second with guaranteed capacity and sub-second latency. 在专用群集中创建的命名空间和事件中心不仅包括标准产品/服务的所有功能,而且不存在任何引入限制。Namespaces and event hubs created within the Dedicated cluster include all features of the Standard offering and more, but without any ingress limits. 它还免费随附了热门的事件中心捕获功能,可让你自动批处理数据流并将其记录到 Azure 存储或 Azure Data Lake。It also includes the popular Event Hubs Capture feature at no additional cost, allowing you to automatically batch and log data streams to Azure Storage or Azure Data Lake.

群集是按容量单位 (CU) 预配和计费的,并预先分配了 CPU 数量和内存资源量。Clusters are provisioned and billed by Capacity Units (CUs), a pre-allocated amount of CPU and memory resources. 可为每个群集购买 1、2、4、8、12、16 或 20 个 CU。You can purchase 1, 2, 4, 8, 12, 16 or 20 CUs for each cluster. 每个 CU 可以引入和流式传输的量取决于多种因素,例如生产者和使用者的数量、有效负载的形状、流出量速率(有关更多详细信息,请参阅下面的基准检验结果)。How much you can ingest and stream per CU depends on a variety of factors, such as the number of producers and consumers, payload shape, egress rate (see benchmark results below for more details).

Note

默认情况下,所有事件中心群集都支持 Kafka,并支持可由现有基于 Kafka 的应用程序使用的 Kafka 终结点。All Event Hubs clusters are Kafka-enabled by default and support Kafka endpoints that can be used by your existing Kafka based applications. 在群集上启用 Kafka 不影响非 Kafka 用例;没有对应的选项,或者不需要在群集上禁用 Kafka。Having Kafka enabled on your cluster does not affect your non-Kafka use cases; there is no option or need to disable Kafka on a cluster.

为何采用专用形式?Why Dedicated?

专用事件中心为需要企业级容量的客户提供了三个引人注目的优点:Dedicated Event Hubs offers three compelling benefits for customers who need enterprise-level capacity:

单租户可以保证容量,以提供更好的性能Single-tenancy guarantees capacity for better performance

专用群集可保证容量完全可缩放,并能够凭借完全持久的存储空间和亚秒级的延迟引入高达千兆字节的流式数据,从而能够适应任何流量激增情况。A Dedicated cluster guarantees capacity at full scale, and can ingress up to gigabytes of streaming data with fully durable storage and sub-second latency to accommodate any burst in traffic.

对功能的专有访问权限和非专有访问权限Inclusive and exclusive access to features

专用产品/服务包括“捕获”等免费的功能,以及对即将推出的功能(例如“创建自己的密钥”(BYOK))的专有访问权限。The Dedicated offering includes features like Capture at no additional cost, as well as exclusive access to upcoming features like Bring Your Own Key (BYOK). 该服务还为客户管理负载均衡、OS 更新、安全修补程序和分区,因此你可以花更少的时间来维护基础结构,而将更多的时间花在构建客户端功能上。The service also manages load balancing, OS updates, security patches and partitioning for the customer, so that you can spend less time on infrastructure maintenance and more time on building client-side features.

节约成本Cost Savings

在高流入量(大于 100 TU)的情况下,群集的每小时成本比在标准产品/服务中购买相当数量的吞吐量单位的成本要少得多。At high ingress volumes (>100 TUs), a cluster costs significantly less per hour than purchasing a comparable quantity of throughput units in the Standard offering.

事件中心专用层配额和限制Event Hubs Dedicated Quotas and Limits

事件中心专用层产品/服务按固定的月度价格计费,至少使用 4 个小时。The Event Hubs Dedicated offering is billed at a fixed monthly price, with a minimum of 4 hours of usage. 专用层提供标准计划的所有功能,但具有企业规模容量和限制,以满足客户的工作负荷需求。The Dedicated tier offers all the features of the Standard plan, but with enterprise scale capacity and limits for customers with demanding workloads.

功能Feature 标准Standard 专用Dedicated
带宽Bandwidth 20 TU(最多 40 TU)20 TUs (up to 40 TUs) 20 CU20 CUs
命名空间Namespaces 11 每个 CU 5050 per CU
事件中心Event Hubs 每个命名空间 1010 per namespace 每个命名空间 10001000 per namespace
入口事件Ingress events 按每百万个事件支付Pay per million events 已含Included
消息大小Message Size 1000000 字节1 Million Bytes 1000000 字节1 Million Bytes
分区Partitions 每个事件中心 3232 per Event Hub 每个事件中心 10241024 per Event Hub
使用者组Consumer groups 每个事件中心 2020 per Event Hub 每个 CU 无限制,每个事件中心 1000No limit per CU, 1000 per event hub
中转连接Brokered connections 包括 1,000 个,最大 5,000 个1,000 included, 5,000 max 包括 100000 个,最大 100000 个100 K included and max
消息保留期Message Retention 7 天,每个 TU 包含 84 GB7 days, 84 GB included per TU 90 天,每个 CU 包含 10 TB90 days, 10 TB included per CU
捕获Capture 按每小时支付Pay per hour 已含Included

如何加入How to onboard

通过添加或删除 CU,可以在一个月内随时扩展或缩小容量,满足自身需求。You can scale your capacity up or down throughout the month to meet your needs by adding or removing CUs. 专用计划独一无二,它提供了一种亲身实践的加入体验,用户可从事件中心产品团队获得适合自己的灵活部署。The Dedicated plan is unique in that you will experience a more hands-on onboarding from the Event Hubs product team to get the flexible deployment that is right for you. 若要加入此 SKU,请联系支持团队To onboard to this SKU, contact support team.

常见问题FAQs

可以使用群集来做什么?What can I achieve with a cluster?

对于事件中心群集,可以引入和流式传输的数据量取决于各种因素,例如生成者、使用者、引入和处理速率,等等。For an Event Hubs cluster, how much you can ingest and stream depends on various factors such as your producers, consumers, the rate at which you are ingesting and processing, and much more.

下表显示了我们在测试期间实现的基准结果:Following table shows the benchmark results that we achieved during our testing:

有效负载形状Payload shape 接收方Receivers 入口带宽Ingress bandwidth 入口消息Ingress messages 出口带宽Egress bandwidth 出口消息Egress messages TU 总数Total TUs 每个 CU 的 TU 数TUs per CU
100x1KB 批Batches of 100x1KB 22 400 MB/秒400 MB/sec 400k 消息数/秒400k messages/sec 800 MB/秒800 MB/sec 800k 消息数/秒800k messages/sec 400 TU400 TUs 100 TU100 TUs
10x10KB 批Batches of 10x10KB 22 666 MB/秒666 MB/sec 66.6k 消息数/秒66.6k messages/sec 1.33 GB/秒1.33 GB/sec 133k 消息数/秒133k messages/sec 666 TU666 TUs 166 TU166 TUs
6x32KB 批Batches of 6x32KB 11 1.05 GB/秒1.05 GB/sec 34k 消息数/秒34k messages / sec 1.05 GB/秒1.05 GB/sec 34k 消息数/秒34k messages/sec 1000 TU1000 TUs 250 TU250 TUs

测试中使用了以下条件:In the testing, the following criteria was used:

  • 一个专用层事件中心群集使用四个容量单位 (CU)。A dedicated-tier Event Hubs cluster with four capacity units (CUs) was used.
  • 用于引入的事件中心包含 200 个分区。The event hub used for ingestion had 200 partitions.
  • 引入的数据由从所有分区接收数据的两个接收方应用程序接收。The data that was ingested was received by two receiver applications receiving from all partitions.

是否可以纵向扩展/纵向缩减群集?Can I scale up/down my cluster?

创建后,群集将按最少 4 个小时的使用量计费。After creation, clusters are billed for a minimum of 4 hours of usage. 你可以向事件中心团队提交支持请求,请求“纵向扩展或纵向缩减专用群集*”以改变群集规模。You can submit a support request to the Event Hubs team to Scale Up or Scale Down Dedicated Cluster* to scale your cluster up or down. 完成纵向缩减群集的请求最多可能需要 7 天。It may take up to 7 days to complete the request to scale down your cluster.

如何将异地灾难恢复应用于群集?How will Geo-DR work with my cluster?

可以将专用层群集下的命名空间与专用层群集下的另一个命名空间进行异地配对。You can geo-pair a namespace under a Dedicated-tier cluster with another namespace under a Dedicated-tier cluster. 不鼓励将专用层命名空间与标准产品/服务中的命名空间配对,因为吞吐量限制不兼容,会导致出错。We do not encourage pairing a Dedicated-tier namespace with a namespace in our Standard offering, since the throughput limit will be incompatible which will result in errors.

是否可以迁移标准命名空间,以使其属于专用层群集?Can I migrate my Standard namespaces to belong to a Dedicated-tier cluster?

目前,我们不支持将事件中心数据从标准命名空间迁移到专用命名空间的自动迁移过程。We do not currently support an automated migration process for migrating your event hubs data from a Standard namespace to a Dedicated one.

后续步骤Next steps

请与 Azure 销售代表或 Azure 支持部门联系,获取有关事件中心专用容量的其他详细信息。Contact your Azure sales representative or Azure Support to get additional details about Event Hubs Dedicated Capacity. 还可访问以下链接,了解有关事件中心定价层的详细信息:You can also learn more about Event Hubs pricing tiers by visiting the following links:

  • 专用事件中心定价Event Hubs Dedicated pricing. 还可以与 Azure 销售代表或 Azure 支持部门联系,获取有关事件中心专用容量的其他详细信息。You can also contact your Azure sales representative or Azure Support to get additional details about Event Hubs Dedicated capacity.
  • 事件中心常见问题解答中包含了定价信息并解答了一些有关事件中心的常见问题。The Event Hubs FAQ contains pricing information and answers some frequently asked questions about Event Hubs.