As a part of our last developer cycle, we added some new best practice guides to our docs, as well as updating some of the existing ones.

In this post, we briefly cover what’s new or improved.

As of CrateDB 2.0, if you are binding to a network reachable IP address, CrateDB performs a number of bootstrap checks during startup. These checks examine your setup and will prevent startup if a problem is detected.

This new best practices guide is intended to help you configure your setup so that CrateDB passes the bootstrap checks and can perform optimally.

If you are binding to the loopback address, the bootstrap checks will not be run, but it is still a good idea to follow these instructions.

Single inserts are typically very fast with CrateDB. A small cluster can easily handle several thousand inserts per second done this way.

However! There is a way to make them faster.

Check out the new best practices guide to learn how batching up your inserts could yield a twofold increase in ingestion performance.

CrateDB provides an easy way to perform a rolling cluster upgrade with zero downtime. We call this a rolling upgrade. And this best practices doc shows you how.

This doc has been around for a while, but it was improved as a part of this work.

You can’t always do a rolling upgrade. For example, when you are upgrading from one feature version to the next. If this is the case, you will have to perform a full restart upgrade. This procedure was not documented before. But now it is. :)

Sharding can take a while to get your head around. Which is why we added this new best practices guide. In it, we show you how to optimize your sharding strategy for either query performance or ingestion performance.

This best practices guide has been a while, but saw an update as a part of this work to show you how to network with CrateDB’s unicast discovery.