​
Onboarding

S2 is available for sign-up in Preview and is currently free unless you incur significant usage (we will get in touch!)

First, login to the dashboard, create a new organization and issue an access token.

​
Get started with the CLI

1

Install the S2 CLI

This method works on macOS and Linux distributions with Homebrew installed.

brew install s2-streamstore/s2/s2

The binary should be installed as s2.

2

Persist your access token

s2 config set --access-token <YOUR-ACCESS-TOKEN-HERE>
3

Create a new basin

Basin names must be globally unique. Try creating a basin with your GitHub handle, something like username-first-basin.

A basin name must be between 8 and 48 characters long and comprise lowercase letters, numbers and hyphens. It cannot begin or end with a hyphen.

export BASIN="<YOUR-BASIN-NAME-HERE>"
s2 create-basin ${BASIN}

Let’s double-check that the new basin is active. You should see its name in the list with an active status:

s2 list-basins
4

Grab your popcorn!

Nothing better than Star Wars to give us a good sense of how we can exercise append and read sessions, and see what data in motion looks like.

We will start by creating a new stream called starwars.

s2 create-stream s2://${BASIN}/starwars

Some of you may have watched the movie in ASCII over telnet from towel.blinkenlights.nl!

We will do the same, except we will “append” the movie to our starwars stream while we also tail it.

Start by creating a read session like so:

s2 read s2://${BASIN}/starwars 2> /dev/null

Open another terminal and start an append session:

export BASIN="<YOUR-BASIN-NAME-HERE>" # Set the basin name for new terminal
nc starwars.s2.dev 23 | s2 append s2://${BASIN}/starwars

Go back to the previous terminal with the read session to enjoy the movie:

​
Estimate your end-to-end latency

1

Create a new stream in a basin with a storage class you intend to use

s2 create-stream s2://${BASIN}/test/express --storage-class express
2

Run the ping test

s2 ping s2://${BASIN}/test/express

Basins are regional in scope, and currently they are always created in aws:us-east-1. So depending on where you are in the world, your latency will vary. More info.

​
Walkthrough