ClickHouse
Run ClickHouse on your own servers for analytics over events, logs, and traces.
RunOS provisions ClickHouse in your RunOS cluster. Use ClickHouse to aggregate large volumes of event data. Keep transactions such as orders and account changes in PostgreSQL if your application needs a transactional store.
Start with the data you expect to query
- Provision ClickHouse from the RunOS Console or CLI. Choose the shard count and replicas per shard for your workload.
- Connect your ingestion job and query client with the service’s connection settings. Set those settings explicitly in the application.
- Load a representative batch of events. Check storage growth and query latency before you choose a production layout.
Replicas help with availability. Plan retention, backups, and a restore test separately. Size storage for both the volume you ingest and the time you need to retain it.
Compare the options in the self-hosted database guide or check the RunOS managed services catalog.