Getting Started with a Hazelcast Client
Not all features are available in all clients.
To find out which features are available in each client, see the feature comparison matrix.
Hundreds or even thousands of clients can be connected to the cluster.
By default, members have
core count * 20 threads that
handle all the requests. For example, if a member has 4 cores, it will have 80 threads available to handle requests.
In client/server topologies, you can serialize your data on the client side before sending it to a member. For example, you can serialize data in JSON and add it to a map. This option is useful if you plan on using Hazelcast to store your data in binary. Clients can handle serialization without the members needing to know how to do so.
For details about why you need to serialize data and the options for doing so, see Serialization.