{"__v":0,"_id":"57a0656019a5850e0096a9b8","api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"body":"Apache Ignite.NET<sup>tm</sup> In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash-based technologies.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/WkzzRftJTgCYmvbRN28x_apache-ignite.png\",\n        \"apache-ignite.png\",\n        \"1024\",\n        \"310\",\n        \"#ec945e\",\n        \"\"\n      ],\n      \"caption\": \"\"\n    }\n  ]\n}\n[/block]\n##Features\nYou can view Ignite as a collection of independent, well-integrated, in-memory components geared to improve performance and scalability of your application. Some of these components include:\n\n  * [Advanced Clustering](doc:cluster)\n  * [Data Grid (Cache)](doc:data-grid) \n  * [Streaming](doc:streaming) \n  * [Compute Grid](doc:compute-grid) \n  * [Service Grid](doc:service-grid)\n  * [Distributed Data Structures](doc:queue-and-set) \n  * [Distributed Messaging](doc:messaging) \n  * [Distributed Events](doc:events)\n\n##Ignite and Ignite.NET\nIgnite.NET is built on top of Ignite:\n* .NET starts the JVM in the same process and communicates with it via JNI & C++\n* .NET, C++ and Java nodes can join the same cluster, use the same caches, and interoperate using common binary protocol\n* Java compute jobs can execute on any node (Java, .NET, C++)\n* .NET compute jobs can only execute on .NET nodes","category":"57a0655f19a5850e0096a9ab","createdAt":"2015-10-08T08:35:00.735Z","excerpt":"In-Memory Data Fabric","githubsync":"","hidden":false,"isReference":false,"link_external":false,"link_url":"","order":0,"parentDoc":null,"project":"56162ab2c8c5e70d00a8a0fd","slug":"getting-started","sync_unique":"","title":"What is Ignite.NET","type":"basic","updates":[],"user":"54d853023c09c11900c7b44d","version":"57a0655f19a5850e0096a9aa","childrenPages":[]}

What is Ignite.NET

In-Memory Data Fabric

Apache Ignite.NET<sup>tm</sup> In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash-based technologies. [block:image] { "images": [ { "image": [ "https://files.readme.io/WkzzRftJTgCYmvbRN28x_apache-ignite.png", "apache-ignite.png", "1024", "310", "#ec945e", "" ], "caption": "" } ] } [/block] ##Features You can view Ignite as a collection of independent, well-integrated, in-memory components geared to improve performance and scalability of your application. Some of these components include: * [Advanced Clustering](doc:cluster) * [Data Grid (Cache)](doc:data-grid) * [Streaming](doc:streaming) * [Compute Grid](doc:compute-grid) * [Service Grid](doc:service-grid) * [Distributed Data Structures](doc:queue-and-set) * [Distributed Messaging](doc:messaging) * [Distributed Events](doc:events) ##Ignite and Ignite.NET Ignite.NET is built on top of Ignite: * .NET starts the JVM in the same process and communicates with it via JNI & C++ * .NET, C++ and Java nodes can join the same cluster, use the same caches, and interoperate using common binary protocol * Java compute jobs can execute on any node (Java, .NET, C++) * .NET compute jobs can only execute on .NET nodes