Deployment

Use Kafka for transaction log and document log persistence.

Use a second local KV instance for durable transaction log and document log persistence. This is not recommended for production systems.

You can rebuild nodes whenever needed as long as the transaction log and document log is durably stored. Nodes will need rebuilding when index formats have breaking changes. Migrating from a Standalone Mode system to a ClusterNode system is possible to address evolving scaling and availability requirements.

Crux does not provide any native security features. It is important that you carefully consider the security risks when deploying Crux in public environments. Contact us if you would like to hear about JUXT’s deployment services for Crux: crux@juxt.pro

JUXT offers a Managed Hosting service for Crux to accelerate your development and provide you with a secure and reliable service. We can deploy into any environment. Contact us if you would like to hear about JUXT’s Managed Hosting service for Crux: crux@juxt.pro

Crux provides utility APIs for local backup and restore when you are using the standalone mode (which is not recommended for production usage). For an example of usage, see the standalone web service example.

An additional example of backup and restore that only applies to a stopped standalone system is provided here.

In a clustered deployment, only Kafka’s official backup and restore functionality should be relied on to provide safe durability. The standalone mode’s backup and restore operations can instead be used for creating operational snapshots of a node’s indexes for scaling purposes.