Re: Distributed Database as best choice for persistence

2018-06-21 Thread Denis Magda
> > Why there exists an official plugin for Cassandra integration then ? To accelerate *existing* Cassandra deployments because Cassandra's in-memory options are not as good as Ignite. If it's a brand new application, then I would use Ignite persistence from the very beginning. Here is you can

Re: Distributed Database as best choice for persistence

2018-06-21 Thread piyush
Thanks Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Distributed Database as best choice for persistence

2018-06-20 Thread dkarachentsev
Hi, Just because: 1) not all users build their apps from scratch, they might have some legacy code built over Cassandra DB; 2) native persistence featured much later than Cassandra module, and there is no point to remove it now; 3) it's always better to offer more choices to user. Anyway,

Re: Distributed Database as best choice for persistence

2018-06-20 Thread piyush
>> What's the point of scaling persistence manually over allowing Ignite to scale both RAM and disk layers for you? Why there exists an official plugin for Cassandra integration then ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Distributed Database as best choice for persistence

2018-06-19 Thread Denis Magda
What's the point of scaling persistence manually over allowing Ignite to scale both RAM and disk layers for you? So, if to answer your question set in the subj, Ignite persistence is the best scalable and strongly consistent disk option for Ignite. If you need Multi DC or backups, then you can

Re: Distributed Database as best choice for persistence

2018-06-19 Thread piyush
>> May I ask why don't you want to go for Ignite persistence? To operate and scale the storage layer independently and process related to it like Compaction for example. I intent to bundle WebServer (Netty) + Application Server (Netty) + DB Engine (Ignite) + Cache in single deployable jar

Re: Distributed Database as best choice for persistence

2018-06-18 Thread Denis Magda
No, you can't make Cassandra transactional by glueing it with Ignite. If you'd like to have transactions, then a strongly consistent store has to be used instead (like RDBMS or Ignite persistence). May I ask why don't you want to go for Ignite persistence? -- Denis On Mon, Jun 18, 2018 at 2:09

Re: Distributed Database as best choice for persistence

2018-06-18 Thread piyush
cool. Does it maintain transactions ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Distributed Database as best choice for persistence

2018-06-18 Thread dkarachentsev
Hi, Probably the best choice would be Cassandra as Ignite has out of the box integration with it [1]. [1] https://apacheignite-mix.readme.io/v2.5/docs/ignite-with-apache-cassandra Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Distributed Database as best choice for persistence

2018-06-18 Thread piyush
which is best choice of distributed persistence for Ignite if we dont want to use native persistence ? Riak ? Cassandra ? Dynamo DB ? Has anyone tried this ? what was the experience ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/