ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface
Date Tue, 16 Feb 2016 21:07:41 GMT
Hi Gareth,

gcollins wrote
> I guess the SpiQuery can help me part of the way potentially, but it
> doesn't give me the control to manage internal memory structure,
> replication, custom persistence etc.

What kind of control do you expect? Can you give an example? In general,
almost everything in Ignite is customizable and pluggable. E.g., to
customize backup node assignments you can implement your own
AffinityFunction, for custom persistence implement CacheStore interface.

Can you clarify what you mean by "internal memory structure"? Can you create
an Ignite cache (or caches) under the hood and provide your own APIs and/or
services around it?


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Migrating-From-Hazelcast-Service-Interface-To-Apache-Ignite-Service-Interface-tp2970p3045.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message