Is Ignite worth using in its current state in production? Is it mature enough?

[zshamrock <al...@gmail.com>]

Hi, guys. The more I use Ignite in our system, the more it feels to me like
not yet enough mature product. I see lots of performance complains in the
discussion, people talking about basic essentials things are not working
properly. No one has a clear performance benchmark, just marketing promises.

Also, I see some critical issues (or even blocker issues) are not being
fixed immediately. Obviously, it is an open source, and if someone wants the
production quality product they should buy GridGain Professional or
Enterprise. 

So, question then is: what is the purpose of Apache Ignite product/project
if it can't be used safely/trustedly in production? Is it just a marketing
effort towards GridGain?

Don't get me wrong. We already invested lots of time and resources into
making Ignite the core part of our product, and will continue using it. As
this is the overall experience so far, that the quality/maturity of the
Apache Ignite is not there yet.

Is anybody aware of any product using Apache Ignite in production? Not
GridGain, but Apache Ignite?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[vkulichenko <va...@gmail.com>]

Hi Jason,

I will not be able to tell you all the details, but this was a IoT use case
which doesn't require a lot of memory and doesn't store a lot of data in
memory, but has strict SLAs on throughput and latency under load. Each
incoming event triggered 2-3 atomic cache operations (get/put/invoke).
Updates were persisted to Cassandra using write-through.
In the benchmark we were running, the whole system was able to process
million events per seconds. I don't remember the numbers for latency, but
they were within production SLAs.

As for the large clusters, I recommend to try it and see how it behaves in
production environment. You can also refer to this page for some tuning
tips: https://apacheignite.readme.io/docs/preparing-for-production

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6898.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[Jason <fq...@outlook.com>]

Thanks Val for your sharing.

>> The same goes for data size and latency/throughput. The latter scales
>> well and I personally was participating in a project where we achieved
>> million operations per second on around 30 servers cluster.

For this project of 30 servers cluster that you participated, can I get more
details?
- What's the running version, Java or .net? Dev language, C# or Java?
- What's the total data volume? 
- What's the real used memory per node?
- How big is the data key/value?
- What's the peak read/write QPS of this scenario?
- More details about the usage? like streamer? Entry Processor? Sql query?
or just put/get?
- What's the 90%-tile and 99%-tile latency?
- Completely in memory? 7x24?
- What's the consistency requirement?
- For million operations per second, what's the atomicity and sync mode,
ATOMIC and FULL_ASYNC?

BTW, if we want to run a cluster with over 200 servers and 1T-2T data
volume, is there any special guide/suggestion?

Thanks,
-Jason



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6866.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[vkulichenko <va...@gmail.com>]

Jason,

All these numbers vary a lot. For example, as for cluster sizes, I know
examples of single-node usages, and of the clusters containing hundreds of
server nodes and thousands of clients. The same goes for data size and
latency/throughput. The latter scales well and I personally was
participating in a project where we achieved million operations per second
on around 30 servers cluster. With more server it could easily be more.

Windows is used as much as Linux. Since this is Java, there is no much
difference.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6864.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[Jason <fq...@outlook.com>]

Thanks Val.

would you like to share some production use data for the Apache.Ignite if
convenient? E.g. for Data fabric in memory, the max cluster nodes number
(client & server respectively),  the rough data volume in memory and some
performance number like latency/throughput in big data?

BTW, is Ignite widely used in Windows server?

Thanks,
-Jason




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6833.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[zshamrock <al...@gmail.com>]

Thank you, for the feedback, Val. Noticed, 1.7.0 version was released! Great
job!



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6831.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[vkulichenko <va...@gmail.com>]

Hi,

Both Apache Ignite and GridGain are widely used in production for various
use cases. Actually, GridGain is fully based in Ignite and shares the whole
codebase with all its issues and problems.

I personally think that most of the issues that users have are caused by
incorrect usage. Ignite (like any other distributed system) requires a lot
of tuning when used under high load, but the documentation is far from being
perfect. When all issues are solved, Ignite can be very performant and
stable, but sometimes it takes time to achieve this.

Overall, I think it's a very mature product and it's being constantly
improved, both in code and in documentation.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6824.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.