Astra Streaming
Unified event streaming, queuing, and pub sub
Delivered as a fully-managed SaaS with boundless scale, massive throughput and low latency. Astra Streaming is the simplest way to modernize your event driven architecture and turbo charge your data in motion strategy.
Please for enhanced support needs, migrations or other help you might need.
Astra Streaming can also be purchased through the , or marketplaces. →
ENTERPRISE | |||
|---|---|---|---|
| Support Type | 24x7 | ||
| Support Goals | |||
| Low Response Time | 24 hours | ||
| Normal Response Time | 24 hours | ||
| High Response Time | 4 hours | ||
| Urgent Response Time | 1 hour | ||
| Price | 15% of monthly usage | ||
How Astra Streaming Billing Works
Pricing is simple from start to scale.
Pay as you go
Astra Streaming pricing is simple and transparent, based on the bandwidth of streaming data, storage and namespaces/topics
Auto-scaling
Astra Streaming compute and storage scales automatically and granularly as demand changes
Zero Ops
Save significant engineering and operations effort typically spent on provisioning, monitoring, scaling and performance tuning.
Metering Details
| Usage | Billing Unit | Metering Details |
|---|---|---|
Write Bandwidth | The “Write Bandwidth” is based on the payload size of each streaming write. RabbitMQ clients will incur a “RabbitMQ Write Bandwidth” charge in addition to the standard “Write Bandwidth” charge. | The minimum message byte size is 512 bytes. Messages smaller than 512 bytes will be charged as if they were 512-byte messages. |
Read Bandwidth | The “Read Bandwidth” is based on the payload size of each streaming read. RabbitMQ clients will incur a “RabbitMQ Read Bandwidth” charge in addition to the standard “Read Bandwidth” charge. | The minimum message byte size is 512 bytes. Messages smaller than 512 bytes will be charged as if they were 512-byte messages. |
Storage | “Storage” means all messages persisted onto storage disk. | Storage is calculated based on logical storage consumption. Storage is measured in GB per month, using the maximum data stored in the given month for the usage calculation. |
Topic/Partitions | “Topic/Partitions” means the channel used to pass messages published by producers to consumers who process those messages. | Topic-partitions are measured per hour. |
Function Instances | A “Function Instance” means a unit used for scaling Pulsar functions or Pulsar IO connectors running on Astra Streaming. | Each Function Instance is assigned a specific amount of CPU and memory which can be allocated to a Pulsar function. Each Pulsar function running on Astra Streaming will have a minimum of one Function Instance allocated to it. Function instances are measured per hour. |
Function Read Bandwidth | “Function Read Bandwidth” is based on the payload size of each function read. | Function read bandwidth is the egress traffic measured in GB coming out of a function (or connector). |
Function Write Bandwidth | “Function Write Bandwidth” is based on the payload size of each function write. | Function write bandwidth is the ingress traffic measured in GB coming into a function (or connector). |
Metrics Read | The “Metrics Read” is based on the payload size of each streaming metrics read. | Metrics reads are measured in GB. |
Metering Unit Rates
| Standard | Americas | Emea |
|---|---|---|
Write Bandwidth, RabbitMQ Write Bandwidth (GB) | 0.1100 | 0.1100 |
Read Bandwidth, RabbitMQ Read Bandwidth (GB) | 0.0400 | 0.0400 |
Storage (GB/month) | 0.1600 | 0.1500 |
Topic/Partitions (topic-partition hours) | 0.0012 | 0.0012 |
Function Instances (function instance hours) | 0.0170 | 0.0180 |
Function Read Bandwidth (GB) | 0.1100 | 0.1100 |
Function Write Bandwidth (GB) | 0.0400 | 0.0400 |
Metrics Read (GB) | 0.1100 | 0.1100 |