CODEWITHSUNDEEP
hazelcast
rattaman
rattaman

Reputation: 556

The proper way of defining map loaders from application - hazelcast

I have an application using Hazelcast in the embedded mode. I use MapLoaders and indexes. I want to change my application so I can use an existing external Hazelcast cluster to which I will connect using the client api and here lies my problem. There is no way of defining those map loaders in the client app, so I need to use the server mode. Right now I'm using the JoinConfig so I can join the cluster and define my map loaders, but if I understand correctly, by joining the cluster my app will become a part of the cluster itself (and host some data partitions) and this is something I would like to avoid. So is there another way of connecting to this external cluster so my app doesn't start hosting the cache data, or is my approach correct and I shouldn't mind being a part of the cluster?

Upvotes: 1

Views: 68

Answers (1)

Rafał Leszko
Rafał Leszko

Reputation: 5531

If you use Hazelcast Client, it just connects to the cluster, but it does not become part of the cluster. It seems like what you want.

Concerning Map Loaders, please check the related code sample.

Upvotes: 1

Related Questions