In general it's hard to recommend Kudu for a MySQL workload that needs more scale, because Kudu currently doesn't have transactions. It's hard to say much beyond that without more specific details about the workload. Kudu will get great performance compared to MySQL or HBase on analytic workloads which need real time writes, but if transactions are required there's only so much that can be done.
- Dan On Wed, May 17, 2017 at 1:59 PM, Cheyenne Forbes < cheyenne.osanu.for...@gmail.com> wrote: > I am building a platform similar to facebook, if facebook was being built > in 2017 and wanted to use something instead of mysql to store users, posts, > likes, comments and messages would you recommend using Kudu over Hbase in > this case? > > Regards, > > Cheyenne O. Forbes > > On Wed, May 17, 2017 at 3:41 PM, Dan Burkert <danburk...@apache.org> > wrote: > >> The closest thing that exists right now is the Impala or SparkSQL >> integrations. As far as I know the targeted use cases are a little >> different, with Phoenix more focussed on OLTP workloads and Kudu targeting >> analytic workloads, at least on the read side. >> >> - Dan >> >> On Wed, May 17, 2017 at 1:26 PM, Cheyenne Forbes < >> cheyenne.osanu.for...@gmail.com> wrote: >> >>> Are there any Plans of a "SQL skin" for Kudu? Similar to Phoenix for >>> Hbase >>> >>> Regards, >>> >>> Cheyenne O. Forbes >>> >> >> >
