StreamNative Cloud - Getting Started

Guide Overview

1. Why StreamNative Cloud?
2. Before You Get Started
3. Identify Your Cluster Needs
4. Connect an Application to StreamNative Cloud
5. Notes On Beta
6. How to Use StreamNative Cloud
7. A Step-by-Step on Getting Started
8. Pricing
9. StreamNative Getting Started Video Tutorial

1. Why StreamNative Cloud?

StreamNative Cloud offers a simple and fast solution for companies looking to adopt, or even just to test out Apache Pulsar. StreamNative Cloud works just like the open-source Apache Pulsar, with the same APIs and open-source clients being used to send and receive messages.

StreamNative Cloud makes adopting Pulsar simple and fast. The StreamNative team manages the heavy lifting of operations to ensure your cluster is running and optimized to meet the demands of your application. As the core contributors to Pulsar, the StreamNative team is well-versed in the technology and the perfect partner for you.

2. Before You Get Started

There are two things you need to do before you get started:

1. Identify Your Cluster Needs
2. Setting up a cluster is simple and fast, you can do it in just a few minutes. There are a few pieces of data you will want to gather before you start:
3. Availability requirements
4. Peak write rate
5. Peak read rate
6. Estimated storage capacity

Once you have this data ready, you will want to choose an application, more on that below.

2. Connect an Application to StreamNative Cloud
3. The next step is to select an application to connect to StreamNative Cloud in order to start sending messages. Apache Pulsar has clients for a variety of languages and all are compatible with StreamNative Cloud, but for a quick test, we recommend you start with the included tools in the latest release of the open-source Pulsar distribution, which you can download and simply unpack from http://pulsar.apache.org/download/ or use our homebrew formula at https://github.com/streamnative/homebrew-streamnative.

With the pular-admin and pulsar-client CLI tools installed, our Cloud Manager UI will help you send your first message by generating commands customized for your cluster.

Once you are ready to connect your application, the Cloud Manager UI can also help you get connected with recipes for using the Pulsar Java, Go, C++, Python, and NodeJS clients.

3. Notes on Beta

We are excited to launch StreamNative Cloud beta! In addition to the options and features available today, we have a lot more coming soon. See below for more details.

4. How to Use StreamNative Cloud

StreamNative Cloud provides a fully-managed instance of Apache Pulsar along with a suite of tools to help administrate your cluster, with support for managing:

• Tenants
• Namespaces
• Namespace policies
• Topics
• Permissions

StreamNative Cloud works by creating a cluster exposed on the public internet, secured with TLS encryption and Oauth2 authentication, that your applications can connect and use.

5. A Step-by-Step On Getting Started

The Cloud Management UI has a built-in tour to help you create and connect to your first StreamNative Cloud cluster. We have also included a step by step below to give you a preview of the process.

1. First, create an organization. An organization allows you to invite team members to help manage your cluster.
2. Create a Pulsar instance, which can either be single- or multi-zone. Single-zone clusters are a cost-effective option for most production workloads. For enhanced availability, we recommend a multi-zone cluster that can withstand a zone-wide outage in the underlying cloud provider. (Additional features will come in the future, for example, instances consisting of multiple Pulsar clusters across geographic regions.)
3. Create a Pulsar cluster for your given throughput and storage needs. (You should have these numbers from the prep work you did above.) The Cloud Management UI provides guidance on the capacity you can expect from a given configuration, as well as an estimate of the costs.
4. Create a Service Account and download the credentials. The credentials will be used to authenticate against the Pulsar Cluster.
5. Grant permissions to your Service Account. A newly created Service Account doesn’t have any permissions, so these need to be added. The Cloud Management UI will walk you through authorizing a new role in the default namespace in your Pulsar cluster.
6. Connect and publish your first messages with the pulsar-client CLI tool. The StreamNative Cloud console provides a quickstart of the commands you need to run to publish messages to a test topic.
7. Congratulations! Your Pulsar cluster is provisioned and ready to start processing messages for your applications.

6. Pricing

This section provides price examples on single-AZ and multi-AZ clusters.

The following table lists the pricing for StreamNative cloud service.

Pricing Example - Single-AZ clusters

In this example, we assume you are running a single-AZ Pulsar cluster of two tiny brokers and three tiny bookies in GCP, and your cluster produces 10 GB and consumes 30 GB messages in March. For the tiny node type, the CPU request is 200 mv for each broker and each bookie. The total charge for the single-AZ Pulsar cluster equals the resource charge and the usage charge.

• The resource charge (in hours) = 31 days x 24 hours/day x (0.2 CPU x 2 brokers + 0.2 CPU x 3 bookies) = 744/CPU-hour x $0.05/CPU-hour = $37.2.
• The usage charge consists of the data-in charge and data-out charge.
• Data-in charge = 10 GB x $0.04/GB = $0.4
• Data-out charge = 30 GB x $0.04/GB = $1.2
• The total usage charge = $0.4 (data-in charge) + $1.2 (data-out charge) = $1.6 Therefore, the total charge = $37.2 (resource charge) + $1.6 (usage charge) = $38.8

Pricing Example - Multi-AZ clusters

In this example, we assume you are running a multi-AZ Pulsar cluster of two micro brokers and three micro bookies in GCP, and your cluster produces 100 GB, consumes 300 GB and retains 100 GB messages in March. For the micro node type, the CPU request is 2 v and 1 V for each broker and each bookie respectively. The total charge for the multi-AZ Pulsar cluster equals the resource charge and the usage charge.

• The resource charge (in hours) = 31 days x 24 hours/day x (2 CPU x 2 brokers + 1 CPU x 3 bookies) = 5,208/CPU-hour x $0.05/CPU-hour = $260.4.
• The sage charge consists of the data-in charge, data-out charge, and data-stored charge.
• Data-in charge = 100 GB x $0.11/GB = $11
• Data-out charge = 300 GB x $0.04/GB = $12
• Data-stored charge = 100 GB x 31 days x 24 hours/day = 74400 GB/hour x $0.0001/GB-hour = $7.44
• The total usage charge = $11 (data-in charge) + $12 (data-out charge) + $7.44 (data-stored charge) = $30.44 Therefore, the total charge = $260.4 (resource charge) + $30.44 (usage charge) = $290.84.

7. StreamNative Cloud Getting Started Video

For your convenience, we have also created a video tutorial. This 9-minute video will show you everything you need to get up and running on StreamNative Cloud. Click here to play the video.

Now you’re ready to get started on StreamNative Cloud. Click here to get started. If you have questions, contact us via the support portal or Live chat.

‍