Introduction
Since this document is a direct translation of the official document of Apache Ignite v2.15.0, there is no English language option.
Apache Ignite is a distributed database designed for high-performance computing with in-memory speed.
NOTES
Running Client Nodes Behind NAT
If client nodes are positioned behind a NAT, communication limitations of the protocol prevent server nodes from establishing connections with clients. This includes scenarios where client nodes operate in virtual environments (such as Kubernetes, etc.) and server nodes are deployed elsewhere.
Binary Client Protocol
The Ignite binary client protocol enables user applications to communicate with an existing Ignite cluster without starting a full-fledged Ignite node. An application can connect to the cluster via a TCP socket. Once connected, the application can interact with the Ignite cluster and perform cache operations using this format.
What is GridGrain?
GridGrain is the company that developed Apache Ignite. It has also developed frameworks on top of Apache Ignite, providing enterprise solutions for Apache Ignite. Additionally, GridGrain offers Apache Ignite as a service (SaaS).
For more detailed information about all the topics covered and not covered in this document, you can click here. The headings in this document (as of the date of preparation) align with the official documentation.
For .NET code examples, you can click here.