For information about the decision to use {pulsar}, see Four Reasons Why {pulsar} is Essential to the Modern Data Stack.
{product} is based heavily on technology originally created as part of Kesque. With the launch of {product}, {company} began shutting down the Kesque service and migrated customers to {product}.
{product} has been architected to satisfy the most stringent enterprise requirements around availability, scale, and latency. {product} was built to handle mission critical use cases for Fortune 100 companies across BFSI, Telecommunications, Technology, Retail, Oil and Gas, and Healthcare.
The pricing model also makes {product} accessible to mid market and small/medium business customers who need event stream processing capabilities to run core parts of their business.
And finally {product} offers a user-friendly interface and free tier to satisfy the needs of individual developers and technologists who want to learn more about {pulsar} and data streaming in general.
Change Data Capture (CDC) for {astra_db} uses a {pulsar-short} IO source connector that processes changes from the Cassandra Change Agent through a {pulsar-short} topic. For more information, see developing:astream-cdc.adoc.
Tenants are an isolated administrative unit for which an authorization scheme can be set and a set of clusters can be defined. Each tenant can have multiple namespaces, a logical container for creating and managing a hierarchy of topics. A topic is a named channel for transmitting messages from producers to consumers. A sink feeds data from {product} to an external system, such as {cassandra} or Elasticsearch.