Simplest Chat App Ever with GridGain Continuous Query
Scalable distributed chat app in 13 lines of code? Yes, please!
Tech blog
Scalable distributed chat app in 13 lines of code? Yes, please!
Apache Ignite 3.1 was released last week, and one of the major new features is .NET Compute support. We can now implement compute jobs in .NET, deploy them to the cluster, and call them from any client. Let’s try it out!
Client drivers for distributed systems are much more complicated than traditional database drivers. They need to handle data partitioning, cluster topology changes, failover scenarios, and inevitable network issues. In this post, we’ll explore two approaches we use to write integration tests for the Apache Ignite.NET client.
A recording of my talk at the Ignite Summit 2025 is now available.
Apache Ignite 3.0 has been released recently. This post is a quick and beginner-friendly guide for .NET developers on how to start with the new version.
Old JDK code meets new Intel security feature, JVM + CLR in one process, and a mysterious crash.
ValueTask may seem like a micro-optimization, but it is very important on hot paths, and easy to miss. Last week I’ve learned this the hard way.
Let’s say we want to convert int to short with a bounds check. Is there a difference between checked((short)x) and Convert.ToInt16(x)?
Dynamically building database queries can be necessary for some use cases, such as UI-defined filtering. This can get challenging with LINQ frameworks like EF Core and Ignite.NET.
.NET 7 introduces AOT (finally!), which allows easy interop with any language on any OS. To demonstrate the possibilities, let’s bring some Ignite APIs to Rust!