+1 2020-11-24 11:33 GMT+03:00, Anton Vinogradov <a...@apache.org>: > +1 > > On Tue, Nov 24, 2020 at 10:24 AM Pavel Tupitsyn <ptupit...@apache.org> > wrote: > >> +1 >> >> On Tue, Nov 24, 2020 at 3:25 AM Saikat Maitra <saikat.mai...@gmail.com> >> wrote: >> >> > +1 >> > >> > On Mon, Nov 23, 2020 at 4:55 PM Valentin Kulichenko < >> > valentin.kuliche...@gmail.com> wrote: >> > >> > > +1 >> > > >> > > On Mon, Nov 23, 2020 at 2:44 PM Denis Magda <dma...@apache.org> >> > > wrote: >> > > >> > > > Igniters, >> > > > >> > > > With this vote, I'd like to formally wrap up our discussion on >> defining >> > > > Ignite as a "distributed database" instead of an "in-memory >> computing" >> > > > platform. See the following discussion for the rationale and >> > > > context: >> > > > >> > > > >> > > >> > >> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Renaming-Ignite-s-product-category-td49246.html >> > > > >> > > > If the vote passes, the website will define Ignite as "a >> > > > distributed >> > > > database for in-memory speed at petabyte scale" to underscore our >> > > in-memory >> > > > origins (and the primary reason why the project is selected) but >> > > > not >> > > > diminishing our persistence capabilities. All prominent use cases >> such >> > as >> > > > caching, high-performance computing, etc. will remain visible on >> > > > the >> > > > website. There is nothing wrong if a distributed database is used >> > > > as >> a >> > > > cache or high-performance compute cluster; it's up to an >> > > > application >> > > > developer to decide. >> > > > >> > > > Overall, please cast your vote for defining Ignite as a >> > > > "distributed >> > > > database": >> > > > +1 - support the change >> > > > -1 - disagree with the change, explain why >> > > > 0 - neutral >> > > > >> > > > This is a majority vote that is open for the next 7 days and to be >> > closed >> > > > on Monday, Nov 30th: >> > > > https://www.timeanddate.com/countdown/to?year=2020&month=11&day=30 >> > > > >> > > > - >> > > > Denis >> > > > >> > > >> > >> >
-- Best regards, Ivan Pavlukhin
