This tutorial assumes you are starting from fresh and have no existing BookKeeper or ZooKeeper data.
If you already have an existing BookKeeper or ZooKeeper cluster, you can checkout the deploy section
for more details on how to deploy a production cluster.

DistributedLog uses ZooKeeper as the metadata store and BookKeeper as the log segment store. So
you need to first start a zookeeper server and a few bookies if you don't already have one. You can
use the dlog script in distributedlog-proxy-server package to get a standalone bookkeeper sandbox. It
starts a zookeeper server and N bookies (N is 3 by default).

// Start the local sandbox instance at port `7000`
> ./distributedlog-proxy-server/bin/dlog local 7000
DistributedLog Sandbox is running now. You could access distributedlog://127.0.0.1:7000

Before using distributedlog, you need to create a distributedlog namespace to store your own list of
streams. The zkServer for the local sandbox is 127.0.0.1:7000 and the bookkeeper's ledgers path is
/ledgers. You could create a namespace pointing to the corresponding bookkeeper cluster.

The distributedlog tutorial also has a multi-streams writer that will take input from a console and write it out
as records to the distributedlog write proxy. Each line will be sent as a separate record.

Run the writer and type a few lines into the console to send to the server.