Druid includes a set of reference configurations and launch scripts for single-machine deployments:
nano-quickstartmicro-quickstartsmallmediumlargexlargeThe micro-quickstart is sized for small machines like laptops and is intended for quick evaluation use-cases.
The nano-quickstart is an even smaller configuration, targeting a machine with 1 CPU and 4GiB memory. It is meant for limited evaluations in resource constrained environments, such as small Docker containers.
The other configurations are intended for general use single-machine deployments. They are sized for hardware roughly based on Amazon's i3 series of EC2 instances.
The startup scripts for these example configurations run a single ZK instance along with the Druid services. You can choose to deploy ZK separately as well.
The example configurations run the Druid Coordinator and Overlord together in a single process using the optional configuration druid.coordinator.asOverlord.enabled=true, described in the Coordinator configuration documentation.
While example configurations are provided for very large single machines, at higher scales we recommend running Druid in a clustered deployment, for fault-tolerance and reduced resource contention.
bin/start-nano-quickstartconf/druid/single-server/nano-quickstartbin/start-micro-quickstartconf/druid/single-server/micro-quickstartbin/start-smallconf/druid/single-server/smallbin/start-mediumconf/druid/single-server/mediumbin/start-largeconf/druid/single-server/largebin/start-xlargeconf/druid/single-server/xlarge