The Java Thin Client exposes Binary Client Protocol features to Java developers.
Unlike Ignite Client nodes, the Thin Client:
- 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.