Category | Feature | Serverless | Dedicated | BYOC | BYOC Pro |
---|---|---|---|---|---|
Cluster Service | Single AZ Clusters | N/A | Yes | Yes | Yes |
Multi-AZ Clusters | Yes | Yes | Yes | Yes | |
Uptime SLA | 99.95% | 99.95% Single AZ / 99.99% Multi AZ | 99.95% Single AZ / 99.99% Multi AZ | 99.95% Single AZ / 99.99% Multi AZ | |
Unlimited Pulsar Clusters | Yes | Yes | Yes | Yes | |
Autoscaling | On by default | Configurable | Configurable | Configurable | |
Classic Engine | Yes | Yes | Yes | Yes | |
Ursa Engine | Coming Soon | Coming Soon | Yes (Public Preview) | Yes (Public Preview) | |
Geo-Replication | Yes | Yes | Yes | Yes | |
Infrastructure & Provisioning & Network Connectivity | Supported Cloud Providers | AWS, GCP, Azure | AWS, GCP, Azure | AWS, GCP, Azure | AWS, GCP, Azure |
Choose any cloud region | No | No¹ | Yes | Yes | |
Dedicated VPC | No | Yes | Yes | Yes | |
Private Link | No | Pro only | Yes | Yes | |
VPC/VNet Peering | No | Pro only | No | Yes | |
Transit Gateway | No | Pro only | No | Yes | |
Observability | Metrics API | Yes | Yes | Yes | Yes |
Remote writes to external observability systems | No | Pro only | No | Yes | |
Maintenance & Operations | Custom Maintenance Window | Production or Enterprise Support Plan tier only | Production or Enterprise Support Plan tier only | Production or Enterprise Support Plan tier only | Production or Enterprise Support Plan tier only |
Multi-Protocol Support | Pulsar | Yes | Yes | Yes | Yes |
Kafka | Yes | Yes | Yes | Yes | |
MQTT | Yes | Yes | Yes | Yes | |
WebSocket | Yes | Yes | Yes | Yes | |
REST | Yes | Yes | Yes | Yes | |
Connectivity and Processing | Pulsar IO (Built-in & Custom) | Yes | Yes | Yes | Yes |
Kafka Connect (Built-in & Custom) | Yes | Yes | Yes | Yes | |
Pulsar Functions | Yes | Yes | Yes | Yes | |
Managed Flink | No | Pro only (Private Preview, GCP only) | Yes (Private Preview) | Yes (Private Preview) | |
Data Storage | Tiered Storage | Transparent | Transparent | Your Bucket | Your Bucket |
Data Backup and Recovery | No | No | No | yes | |
Security | Multi-tenancy | Yes | Yes | Yes | Yes |
Authentication | Yes | Yes | Yes | Yes | |
Authorization | Yes | Yes | Yes | Yes | |
Audit Logs | Yes | Yes | Yes | Yes | |
Data-at-rest Encryption | Yes | Yes | Yes | Yes | |
TLS Encryption | Yes | Yes | Yes | Yes | |
End-to-end Encryption | Yes | Yes | Yes | Yes | |
Bring Your Own Key | No | Pro only | No | Yes |
Dimension | Minimum | Maximum |
---|---|---|
ETUs | 0 | 20 |
Dimension | ETU Capacity |
---|---|
Ingress (Data In) | 5 megabytes per second (MBps) |
Egress (Data Out) | 15 megabytes per second (MBps) |
Data Entries | 500 entries per second |
Dimension | Capability | Additional details |
---|---|---|
Ingress (Data In) | Max 100 MBps | Number of bytes that can be produced to the cluster in one second. To reduce usage on this dimension, you can compress your messages. lz4 is recommended for compression. |
Egress (Data Out) | Max 300 MBps | Number of bytes that can be consumed from the cluster in one second. To reduce usage on this dimension, you can compress your messages and ensure each consumer is only consuming from the topics it requires. lz4 is recommended for compression. |
Data Entries | Max 10,000 per second | Number of data entries produced to and consumed from the cluster in one second. Each data entry represents a batch of messages. Both Pulsar and Kafka clients do batching at the client side. To reduce usage on this dimension, you can adjust producer batching configurations and shut down otherwise inactive clients. |
Dimension | Capability |
---|---|
Ingress per partition | 5 MBps |
Egress per partition | 15 MBps |
Storage per partition | Unlimited |
Dimension | Capability | Additional details |
---|---|---|
Ingress | Max 100 MBps | Number of bytes that can be produced to the cluster in one second. To reduce usage on this dimension, you can compress your messages. lz4 is recommended for compression. |
Egress | Max 300 MBps | Number of bytes that can be consumed from the cluster in one second. To reduce usage on this dimension, you can compress your messages and ensure each consumer is only consuming from the topics it requires. lz4 is recommended for compression. |
Storage | Unlimited | Number of bytes retained on the cluster, pre-replication. You can configure retention policy settings at namespace or topic level so you can control exactly how much and how long to retain data in a way that makes sense for your applications and helps control your costs. To reduce usage on this dimension, you can compress your messages and reduce your retention settings. lz4 is recommended for compression. |
Data Entries | Max 10,000 per second | Number of data entries produced to and consumed from the cluster in one second. Each data entry represents a batch of messages. To reduce usage on this dimension, you can adjust producer batching configurations and shut down otherwise inactive clients. |
Message size | Max 5 MB | None |
Identifier | Location |
---|---|
ap-southeast-2 | Asia Pacific (Sydney) |
eu-central-1 | Europe (Frankfurt) |
eu-west-1 | Europe (Ireland) |
us-east-2 | US East (Ohio) |
Identifier | Location |
---|---|
europe-west1 | St. Ghislain, Belgium, Europe |
us-central1 | Council Bluffs, Iowa, North America |
Identifier | Location |
---|---|
eastus | US East |
Type | Features | Capability |
---|---|---|
Service | Uptime SLA | 99.95% |
Multi AZ | 99.99% | |
Scale | Throughput limit per topic | Max 100 MBps |
Storage limit per topic | Max 1000 TB | |
Tenant limit | Max 128 | |
Namespace limit | Max 1024 | |
Topic limit | Max 10240 | |
Cloud providers | GCP | Yes |
AWS | Yes | |
Azure | Yes |
Dimension | ETU Capacity |
---|---|
Ingress (Data In) | 25 megabytes per second (MBps) |
Egress (Data Out) | 75 megabytes per second (MBps) |
Data Entries | 2500 entries per second |
Dimension | ETU Capacity |
---|---|
Ingress (Data In) | 25 megabytes per second (MBps) |
Egress (Data Out) | 75 megabytes per second (MBps) |
Data Entries | 2500 entries per second |