You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "Paulus de B." <w....@knollenstein.com> on 2018/01/05 16:56:30 UTC
Limited use without rolling upgrades and backups?
We are thinking about moving our main databases from MySQL Cluster /
Aerospike / Elastic search to Ignite and only two things prevent us from
doing so:
- upgrading to new versions without down time (rolling upgrades)
- creating backups ('snapshots')
I know we can get paid options for this (and yes, I checked the price, a bit
to hefty for us), but most open source databases (like MySQL and Aerospike)
support rolling upgrades and backups out of the box. Not having these two
features limits the application of Ignite.
Just wanted to know if there are any plans or ideas around this, because I
really think Ignite is on the something with the SQL / key value store
combination. Would be a shame if this incredible open source technology can
only be used for systems that can be taking offline completely and don't
need backups.
Paulus.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Limited use without rolling upgrades and backups?
Posted by Denis Magda <dm...@apache.org>.
Hello Paulus,
That’s true that Ignite misses these capabilities at the moment and there are no any movements on the community side or sponsors/committers who would like to bring the features to the project.
Probably the situation will be changed in the future, so let’s wait and see how it goes.
—
Denis
> On Jan 5, 2018, at 8:56 AM, Paulus de B. <w....@knollenstein.com> wrote:
>
> We are thinking about moving our main databases from MySQL Cluster /
> Aerospike / Elastic search to Ignite and only two things prevent us from
> doing so:
> - upgrading to new versions without down time (rolling upgrades)
> - creating backups ('snapshots')
>
> I know we can get paid options for this (and yes, I checked the price, a bit
> to hefty for us), but most open source databases (like MySQL and Aerospike)
> support rolling upgrades and backups out of the box. Not having these two
> features limits the application of Ignite.
>
> Just wanted to know if there are any plans or ideas around this, because I
> really think Ignite is on the something with the SQL / key value store
> combination. Would be a shame if this incredible open source technology can
> only be used for systems that can be taking offline completely and don't
> need backups.
>
> Paulus.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/