Pulsar is a messaging and streaming platform that scales across organizations of all sizes. Pulsar APIs are the core building blocks of Pulsar, which allow you to interact with Pulsar or administer Pulsar clusters. Pulsar APIs consist of the following types:
When to use Pulsar APIs
Pulsar client APIs and Pulsar admin APIs serve two different purposes in the Pulsar API design. You can use Pulsar client APIs to build applications with Pulsar and use Pulsar admin APIs to manage Pulsar clusters.
Here is a simple comparison between Pulsar client APIs and Pulsar admin APIs.
|Category||Pulsar client APIs||Pulsar admin APIs|
|Goals||Build applications with Pulsar||Administer Pulsar clusters|
|Use cases||Pulsar client APIs help you create applications that rely on real-time data. |
For example, you can build a financial application to handle fraud alerts or an eCommerce application that creates recommendations based on user activities.
|Pulsar administration APIs let you administer the entire Pulsar instance, including clusters, tenants, namespaces, and topics, from a single endpoint. |
For example, you can configure security and compliance, or get information about brokers, check for any issues, and then troubleshoot solutions.
|Key features||- Process data with producers, consumers, readers, and TableView |
- Secure data with authentication and authorization
- Protect data with transactions and schema
- Stabilize data with cluster-level auto failover
|- Configure authentication and authorization |
- Set data retention and resource isolation policies
- Facilitate workflow of application development
- Troubleshoot Pulsar
|Interfaces||- Java client API |
- C++ client API
- Python client API
- Go client API
- Node.js client API
- WebSocket client API
- C# client API
|- Java admin API |
- REST API