ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface
Date Tue, 16 Feb 2016 23:55:03 GMT
On Tue, Feb 16, 2016 at 12:00 PM, collins <gareth.o.collins@gmail.com>
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.
>
> The Hazelcast API I am referring to is described in chapter 24 of the
> Hazelcast Manual (Extending Hazelcast - User Defined Services). This
> API was added when they released Hazelcast 3.0. As part of this
> release, they also rewrote all their internal data structures (e.g.
> Map, Queue etc) to use this same API so that you can write a service
> that can do anything their internal data structures can do.
>

Hm… I am not sure I fully understand. Why not just create caches or data
structures internally within Ignite service and make use of them in your
service logic? What am I missing?

D.

Mime
View raw message