46 ms·
Do you support only transitive aggregation operations? If so why not push the entire aggregation to elasticsearch/cadsandra? How do you plan to scale cpu wise?
by itaifrenkel 11y ago
Do you support only transitive aggregation operations? If so why not push the entire aggregation to elasticsearch/cadsandra?
How do you plan to scale cpu wise? ES and streaming engines (dont know cassandra) are cpu hogs (compared to map reduce).
I heard at devopsdays Tel Aviv that bigpanda decided to provide different sla to paying and non paying customers to balance the costs.
- deleted 11y ago[deleted]
- henridf 11y agoThe Juttle query language allows the expression of dataflow graphs and UDFs which can not (in general) be done natively in ES. As far as the scaling issue goes, this was designed to run on premise rather than as a SaaS service (unlike bigpanda?). Disclaimer on last paragraph: as per @demmer's comment below, Jut's plans have changed, so it may no longer be valid or relevant.