Ivan,

That's right, 78 Ignite practitioners took part in the poll. As for this
feedback below,

*Apache Ignite was close to a drop-in replacement technology for a*
*home grown memory-centric data grid used in a legacy product which*
*allowed us to concentrate on building more customer value rather than*
*infrastructure.*

this happens frequently; Ignite is still primarily used as an in-memory
caching and compute layer for existing services, APIs and databases.
Companies inject Ignite in their solutions, load a lot of data, scale and
access with SQL, compute, etc. A sort of in-memory data management platform
or integration hub if to use the terms of technology analysts.

-
Denis


On Fri, Jan 10, 2020 at 12:56 AM Ivan Pavlukhin <vololo...@gmail.com> wrote:

> Denis,
>
> Great! Am I getting it right that there was about 80 respondents?
>
> чт, 9 янв. 2020 г. в 22:14, Denis Magda <dma...@apache.org>:
> >
> > Ignite dev community,
> >
> > I've closed the questionary and here is raw anonymous data for
> > your reference:
> >
> https://docs.google.com/document/d/1Rkc82GkNlsVrwXxQgFd8RgFNV_qVwuMhmzaQV2W9ccI/edit?usp=sharing
> >
> > Overall, Ignite is continued to be used heavely for caching
> > scenarios (services, DBs, APIs) with increasing usage of SQL and native
> > persistence. Usability and technical issues are mentioned in relation to
> > these two components. Plus, a plenty of other useful thoughts and
> > suggestions.
> >
> > -
> > Denis
> >
> >
> > On Wed, Dec 4, 2019 at 2:51 PM Denis Magda <dma...@apache.org> wrote:
> >
> > > Folks,
> > >
> > > There are many ongoing conversations and activities on the list
> related to
> > > Ignite's evolution (modularization, 3.0, full-text search support,
> etc.).
> > >
> > > I'm suggesting to ask our broader user community to contribute by
> sharing
> > > short feedback and discuss results in several weeks:
> > >
> > >
> https://docs.google.com/forms/d/e/1FAIpQLSdUveEVXer3lpkyiqfFw4175TvZzGHUOS4snPfnkO0NDku0eQ/viewform
> > >
> > > Ultimately, the project is being developed for the purpose and it will
> be
> > > right to hear back from those who put Ignite in prod. Please check the
> > > questionary and suggest any changes. It should be short and compact.
> We'll
> > > send it to the user list and can publish it on the Ignite website.
> > >
> > > -
> > > Denis
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Reply via email to