Alluxio isn't a database though; it's storage. I may be still harping on the wrong solution for you, but as we discussed offline, that's also what Impala, Drill et al are for.
Sorry if this was mentioned before but Ignite is what GridGain became, if that helps. On Sat, Sep 17, 2016 at 11:00 PM, Mich Talebzadeh <mich.talebza...@gmail.com> wrote: > Thanks Todd > > As I thought Apache Ignite is a data fabric much like Oracle Coherence cache > or HazelCast. > > The use case is different between an in-memory-database (IMDB) and Data > Fabric. The build that I am dealing with has a 'database centric' view of > its data (i.e. it accesses its data using Spark sql and JDBC) so an > in-memory database will be a better fit. On the other hand If the > application deals solely with Java objects and does not have any notion of a > 'database', does not need SQL style queries and really just wants a > distributed, high performance object storage grid, then I think Ignite would > likely be the preferred choice. > > So will likely go if needed for an in-memory database like Alluxio. I have > seen a rather debatable comparison between Spark and Ignite that looks to be > like a one sided rant. > > HTH > > > > > Dr Mich Talebzadeh > > > > LinkedIn > https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw > > > > http://talebzadehmich.wordpress.com > > > Disclaimer: Use it at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. The > author will in no case be liable for any monetary damages arising from such > loss, damage or destruction. > > > > --------------------------------------------------------------------- To unsubscribe e-mail: user-unsubscr...@spark.apache.org
