1. why do we need the storage (whether native or 3rd party)? I need the storage because 1) down time for production deployment. 2) the data in the cache may be crashed and All ignite clusters are completed down (sorry)
2. So I need a storage to store the data that have been committed when transactions are committed. Do I have to care MVCC query in 3rd party storage? No. It's very difficult (if not possible) to achieve this goal given people are using distributed NoSQL databases. Can we directly query Ignite native storage with MVCC without the caching layer running on top of it? 3. Comparing to the other database storage, Ignite native storage is relative new. The features to support ML, data mining are provided, but not comprehensive like Apach Spark... So questions are raised when the integration of Ignite native storage or 3rd party storage with Spark - which storage is better? 4. I think that Ignite should specialize in caching, MVCC on cache layer (grid). Provide own native storage, ML, data mining feature are great, but there is limited resource for this community to complete this mission. Leave the other specialized groups (exports) focusing on storage store, ML, data mining, Block Chain... 5. Instead Ignite might focus on to integrate these things together to build data-ecosystem. I think that there are many dis-integrated, separated data storage, cache, ML, Deep Learning, blockchain. To put these things together, it needs visionary leaders, high skilled engineers. Why can we make our world life easier? 6. Igniters, please focus the grid computing (cache), ACID-compliant transaction, MVCC-enabled SQL in cache layer, and provide services to integrate with the other storage, spark (ML), hyper ledge fabric or ethereum or bitcoin (block chain). -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
