Author
Pavel Tupitsyn

Pavel Tupitsyn
Software Engineer at GridGain Systems
Recently a new version of Apache® Ignite™ was released. Let’s examine some of the new features from the .NET perspective.   Thin .NET Client   Before Apache Ignite version 2.4 (in both Java and .NET), there were two cluster connection modes: Server and Client. Basically, the difference between the client mode and server mode boils down to the following: the client nodes don’t store data and…
read more
Recently, I've started seeing the names GridGain and Apache® Ignite™ popping up on the Internet more and more frequently. However, judging from some of the chatter I've seen in social media around these mentions, very few people understand either product -- let alone what each can be used for. In this post, I will try to explain a little about both -- along with some examples. Ignite vs…
read more
Data terabytes, clusters for hundreds of machines, big data, high load, machine learning, microservices... and other scary words are all applicable to Apache® Ignite™. But this does not mean that it is not suitable for less ambitious goals. Today, we'll look at how Ignite can easily store any of your objects, share them over the network, and provide .NET and Java interoperability. We will talk…
read more
Apache® Ignite™ 2.0 was released last week. The changes on the Java side are tremendous, but Ignite.NET has some cool things to offer as well. Let's take a closer look. # Dynamic Type Registration There's no need for anymore for BinaryConfiguration. Types are automatically registered within the cluster. All serialization is now performed in Ignite Binary Format which enables all Ignite features…
read more