Re:SnappyData: OLTP and OLAP Database Built on Apache Spark
by twistedpair on Wednesday February 03, 2016 @03:05PM
(#11029322)
Why add Spark? We run Spark in prod and have to actively patch the code based because there are so many ways to make it crash and burn. LDAP is a solved problem, why add Spark and instability to the mix?
[ Parent
| on HN ]
Re:SnappyData: OLTP and OLAP Database Built on Apache Spark
by sudsmenon on Wednesday February 03, 2016 @03:15PM
(#11029395)
Fundamentally, any enterprise today has to deal with OLTP data, OLAP data (transactional plus other sources), Streaming and finally machine learning. Our premise is that you can choose to use 4 different platforms for each one or move to a unified platform. Spark offers streaming, it offers Spark SQL and there are a bunch of machine learning libraries available on Spark. Also, everyone who has anything to do with data has a connector to Spark so it becomes a good data integration platform. The API is uniform across these. So it forms a good substrate for what we are trying to do. As for bugs, it is a platform that is growing rapidly , going through some growing pains, and over a period of time, it will mature. We believe that the core capabilities will become powerful over time (SparkSQL, Streaming etc.) It is a somewhat opinionated choice but one that we think will pan out over time.
Re:SnappyData: OLTP and OLAP Database Built on Apache Spark
by plamb on Wednesday February 03, 2016 @03:19PM
(#11029424)
Also (correct me if I'm wrong), the stability of SnappyData will depend more on GemFireXD (related to Apache Geode), the in-memory database that has been integrated with Spark to form SnappyData, then it will depend on Spark. GemFire has been in development for over a decade and has a multitude production use cases.