For those of use who love trying before buying, would love to better understand the moving parts and their responsibility --- querying engine, coordinator, and datastore (etc) --- and how they evolve as your scale the systems.
Storage, aggregation and compute are all separate and scale up/down independently. The coordinator and query services are both stateless and you just add more instances, DB nodes do not do compression/decompression for instance all this happens as part of computation on the query service.
M3DB for storage has a k8s operator that can manage clusters (expansion, etc), and the M3 aggregator can be deployed as a stateful set in k8s and also can be independently expanded.