- Is lightweight: there are no new threads, no logging and no local files produced when using thin client operations. The thin client only needs one TCP port to utilise the binary protocol.
- Does not join Ignite cluster: the Thin Client does not become part of the Ignite cluster topology, which brings limitations like limited high-availability, no Java types metadata exchange and no monitoring by Ignite management tools.
- Exposes a subset of the full Ignite API: although the binary protocol is being actively developed with more features added, presently the protocol features represent only a subset of the Ignite data grid.
- Visit Quick Start to learn the basics by developing a simple Ignite thin client application.
- Visit API to check which APIs are currently supported.
- Visit Security to see the Thin Client has enough protection to connect to an enterprise Ignite cluster over Internet.
- Visit High Availability to learn how fault tolerance is provided.
- Visit Monitoring to learn how failures are reported.
Updated 2 years ago