one more question; compare with DB, is there any tools like migrate, purge and archive data tools?
or we have to implement it in our application code? Regards Aaron [email protected] From: [email protected] Date: 2017-11-02 18:02 To: user Subject: Re: Re: Some concern regards the DataRegionConfiguration of the 2.3 Got thanks Alexey! Regards Aaron [email protected] From: Alexey Kukushkin Date: 2017-11-02 17:43 To: user Subject: Re: Some concern regards the DataRegionConfiguration of the 2.3 Hi, When you said "old memory configuration" did you mean using cacheStoreFactory? Ignite has two persistence options: native and 3rd-party persistence and having cacheStoreFactory configured means you use the latter one. Unlike Ignite native persistence, the 3rd party persistence is slower in most cases, not transparent to SQL, requires explicit initial data load and the associated storage might become a performance or availability issue. But 3rd party persistence allows you to plug Ignite into your existing system between the application and database layers, protecting your investment into other apps using the same database. You can keep using 3rd-party persistence with Ignite 2.3. You might evaluate if you want to migrate to native persistence. Do not use both.
