Along with unit testing, continuous integration, and code review, static code analysis is invaluable for maintaining healthy code base.
Apache Ignite 2.1 has been released last week, introducing Ignite Persistent Store! Another huge step forward for the project: it becomes a complete database with unique feature set, check out the comparison table on ignite.apache.org frontpage. As usual, we’ll have a look at new features from .NET standpoint.
Apache Ignite 2.0 has been released last week. Changes on Java side are tremendous, but Ignite.NET has some cool things to offer as well.
Ignite.NET offers a LINQ provider which translates C# expressions to SQL queries. LINQ has many benefits over SQL, but at what cost?
Apache Ignite 1.9 has been released last week. Let’s see what is new in the .NET part.
Apache Ignite 1.8 has been released yesterday. Let’s see what is new in the .NET part.
Implement Ignite.NET persistent store with Entity Framework and SQL Server.
How fast are different Ignite serialization modes? How do they compare to other popular serializers?
Speed up your ASP.NET web farm with a Apache Ignite distributed caching.
Ignite cluster can consist of nodes on any supported platform: Java, .NET and C++. Let’s see how to run .NET/Java cluster with NuGet and Maven.
LINQPad is a must-have tool for every .NET developer, and it is a great way to explore and try Ignite.NET APIs.
Apache Ignite 1.7 has been released last week. Let’s see what is new in the .NET part.
This part covers cache queries: Scan, SQL, LINQ, and Text.
This part covers basic cache operations and user object serialization.
This post opens a blog series about Apache Ignite.NET, distributed in-memory platform.