I too would love to understand if RestBASE can become our default solution for this kind of data-intensive APIs. Can you guys briefly explain what kind of queries and aggregations would be problematic if we were to go with Cassandra?
> On Jun 9, 2015, at 8:39 AM, Oliver Keyes <[email protected]> wrote: > > Remember that (as things currently stand) putting the thing on labs > means meta-analytics ("how are the cubes being used?") being a pain in > the backside to integrate with our existing storage solutions. > > On 8 June 2015 at 22:52, Dan Andreescu <[email protected]> wrote: >>> As always, I'd recommend that we go with tech we are familiar with -- >>> mysql or cassandra. We have a cassandra committer on staff who would be able >>> to answer these questions in detail. >>> >>> >>> WMF uses PostGRES for some things, no? Or is that is just in labs? >> >> >> Since this data is meant to be fully public and queryable in any way, we >> could put it in the PostgreSQL instance on labs. We should check with labs >> folks, perhaps horse trade some hardware, but I think that would be a >> splendid solution. >> >> However, and I'm trying to understate this in case people are not familiar >> with my hyperbolic style, I'd rather drink Bud Lite Lime than use MySQL for >> this. MySQL is suited for a lot of things, but analytics is not one of >> them. >> >> p.s. I will never drink Bud Lite Lime. Like, never. >> >> _______________________________________________ >> Analytics mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/analytics >> > > > > -- > Oliver Keyes > Research Analyst > Wikimedia Foundation > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics _______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
