Best practice for managing the structure of Couchbase

Couchbase Server
1

What is the best practice for the following related use cases in Couchbase?

Usecases:

  • Enable developers to initialize a Couchbase cluster and all buckets, scopes, collections, indexes and such that is compatible with the code they want to run.
  • Deploy changes to buckets, scopes, etc to staging and production when deploying new code.
  • Apply any recent changes to buckets, scopes to a restored backup that were applied after the backup was taken.

Thanks!

2

There are REST APIs for management https://docs.couchbase.com/server/current/rest-api/rest-intro.html

The SDKs have apis for most of the management APIS.

For changes since the last backup - do another incremental backup. Or use xdcr to keep a standby cluster up-to-date with an.active cluster.

Backups can also be used to copy indexes etc.

Couchbase Testcontainers can be used to spin up a serve for testing.

GitHub - couchbaselabs/cbdinocluster has some pre-configured clusters.

Many Couchbase repositories are public, you can explore wha we do ourselves.

3

Thanks @mreiche! We need something really simple to use for our users. So I think we will need to build something for them.