3 ms·
Rob and team have been working hard to ensure m3db is a long term winner. love to see it. For those of use who love trying before buying, would love to better
by jaren 6y ago
Rob and team have been working hard to ensure m3db is a long term winner. love to see it.
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.
- roskilli 6y agoHey jaren hope things are well at Robinhood. Good question, there's a diagram on what a default deployment looks like alongside the M3 v1.0 announcement https://medium.com/chronosphere/m3-v1-0-released-a-production-ready-prometheus-metrics-store-scalable-to-hundreds-of-nodes-7f673fac4334 https://medium.com/chronosphere/m3-v1-0-released-a-productio... and in depth documentation on the website https://m3db.io/docs/overview/ https://m3db.io/docs/overview/. 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.