You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Pavel Tupitsyn <pt...@apache.org> on 2021/07/16 10:28:00 UTC
Thin client data structures
Igniters,
I was asked a few times about Data Structures [1] in thin clients.
While there are plans to add them eventually, it is possible to implement
them on top of the existing thin client cache API.
I'd like to share a short blog post which demonstrates this [2].
[1] https://ignite.apache.org/features/datastructures.html
[2]
https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
Re: Thin client data structures
Posted by Pavel Tupitsyn <pt...@apache.org>.
Kathryn,
Yes, same thing for the thick client.
Thick API also has ICache.Invoke to perform atomic updates with custom
logic, which can help with implementation in some cases.
On Fri, Jul 16, 2021 at 5:22 PM Kathryn Hogg <Ka...@oati.net> wrote:
> Out of curiosity -- would this be the best approach to take to implement
> data structures for C# thick client as well?
>
>
>
> --
>
> Kathryn Hogg
>
> Principal Technology Architect
>
>
>
> *From:* Ivan Daschinsky [mailto:ivandasch@gmail.com]
> *Sent:* Friday, July 16, 2021 8:59 AM
> *To:* user@ignite.apache.org
> *Subject:* Re: Thin client data structures
>
>
>
> *{External email message: This email is from an external source. Please
> exercise caution prior to opening attachments, clicking on links, or
> providing any sensitive information.}*
>
> Yep, if you have atomic k, v store and events, you definitely can
> implement queue, distributed lock and others primitives :) I'm not against
> it, let it be.
>
>
>
> пт, 16 июл. 2021 г., 16:18 Pavel Tupitsyn <pt...@apache.org>:
>
> Ivan,
>
>
>
> When Ignite is already in use by the app (for caching, SQL, etc),
>
> it makes sense to utilize it for all purposes instead of adding more
> products to the mix.
>
>
>
> Ignite has many features, sometimes you can find product X that does Y
> better,
>
> but you won't find a product that has them all.
>
>
>
> And I'm just trying to demonstrate what is possible :)
>
>
>
> On Fri, Jul 16, 2021 at 3:20 PM Ivan Daschinsky <iv...@gmail.com>
> wrote:
>
> Hi! Pavel, it is fun stuff. But is there any real use case for this
> feature? I'd rather use RabbitMQ for this :)
>
>
>
> пт, 16 июл. 2021 г. в 13:28, Pavel Tupitsyn <pt...@apache.org>:
>
> Igniters,
>
>
>
> I was asked a few times about Data Structures [1] in thin clients.
>
>
>
> While there are plans to add them eventually, it is possible to implement
> them on top of the existing thin client cache API.
>
> I'd like to share a short blog post which demonstrates this [2].
>
>
>
> [1] https://ignite.apache.org/features/datastructures.html
>
> [2]
> https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
>
>
>
>
> --
>
> Sincerely yours, Ivan Daschinskiy
>
>
RE: Thin client data structures
Posted by Kathryn Hogg <Ka...@oati.net>.
Out of curiosity -- would this be the best approach to take to implement data structures for C# thick client as well?
--
Kathryn Hogg
Principal Technology Architect
From: Ivan Daschinsky [mailto:ivandasch@gmail.com]
Sent: Friday, July 16, 2021 8:59 AM
To: user@ignite.apache.org
Subject: Re: Thin client data structures
{External email message: This email is from an external source. Please exercise caution prior to opening attachments, clicking on links, or providing any sensitive information.}
Yep, if you have atomic k, v store and events, you definitely can implement queue, distributed lock and others primitives :) I'm not against it, let it be.
пт, 16 июл. 2021 г., 16:18 Pavel Tupitsyn <pt...@apache.org>>:
Ivan,
When Ignite is already in use by the app (for caching, SQL, etc),
it makes sense to utilize it for all purposes instead of adding more products to the mix.
Ignite has many features, sometimes you can find product X that does Y better,
but you won't find a product that has them all.
And I'm just trying to demonstrate what is possible :)
On Fri, Jul 16, 2021 at 3:20 PM Ivan Daschinsky <iv...@gmail.com>> wrote:
Hi! Pavel, it is fun stuff. But is there any real use case for this feature? I'd rather use RabbitMQ for this :)
пт, 16 июл. 2021 г. в 13:28, Pavel Tupitsyn <pt...@apache.org>>:
Igniters,
I was asked a few times about Data Structures [1] in thin clients.
While there are plans to add them eventually, it is possible to implement them on top of the existing thin client cache API.
I'd like to share a short blog post which demonstrates this [2].
[1] https://ignite.apache.org/features/datastructures.html
[2] https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
--
Sincerely yours, Ivan Daschinskiy
Re: Thin client data structures
Posted by Ivan Daschinsky <iv...@gmail.com>.
Yep, if you have atomic k, v store and events, you definitely can implement
queue, distributed lock and others primitives :) I'm not against it, let it
be.
пт, 16 июл. 2021 г., 16:18 Pavel Tupitsyn <pt...@apache.org>:
> Ivan,
>
> When Ignite is already in use by the app (for caching, SQL, etc),
> it makes sense to utilize it for all purposes instead of adding more
> products to the mix.
>
> Ignite has many features, sometimes you can find product X that does Y
> better,
> but you won't find a product that has them all.
>
> And I'm just trying to demonstrate what is possible :)
>
> On Fri, Jul 16, 2021 at 3:20 PM Ivan Daschinsky <iv...@gmail.com>
> wrote:
>
>> Hi! Pavel, it is fun stuff. But is there any real use case for this
>> feature? I'd rather use RabbitMQ for this :)
>>
>> пт, 16 июл. 2021 г. в 13:28, Pavel Tupitsyn <pt...@apache.org>:
>>
>>> Igniters,
>>>
>>> I was asked a few times about Data Structures [1] in thin clients.
>>>
>>> While there are plans to add them eventually, it is possible to
>>> implement them on top of the existing thin client cache API.
>>> I'd like to share a short blog post which demonstrates this [2].
>>>
>>> [1] https://ignite.apache.org/features/datastructures.html
>>> [2]
>>> https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
>>>
>>
>>
>> --
>> Sincerely yours, Ivan Daschinskiy
>>
>
Re: Thin client data structures
Posted by Pavel Tupitsyn <pt...@apache.org>.
Ivan,
When Ignite is already in use by the app (for caching, SQL, etc),
it makes sense to utilize it for all purposes instead of adding more
products to the mix.
Ignite has many features, sometimes you can find product X that does Y
better,
but you won't find a product that has them all.
And I'm just trying to demonstrate what is possible :)
On Fri, Jul 16, 2021 at 3:20 PM Ivan Daschinsky <iv...@gmail.com> wrote:
> Hi! Pavel, it is fun stuff. But is there any real use case for this
> feature? I'd rather use RabbitMQ for this :)
>
> пт, 16 июл. 2021 г. в 13:28, Pavel Tupitsyn <pt...@apache.org>:
>
>> Igniters,
>>
>> I was asked a few times about Data Structures [1] in thin clients.
>>
>> While there are plans to add them eventually, it is possible to implement
>> them on top of the existing thin client cache API.
>> I'd like to share a short blog post which demonstrates this [2].
>>
>> [1] https://ignite.apache.org/features/datastructures.html
>> [2]
>> https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
>>
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>
Re: Thin client data structures
Posted by Ivan Daschinsky <iv...@gmail.com>.
Hi! Pavel, it is fun stuff. But is there any real use case for this
feature? I'd rather use RabbitMQ for this :)
пт, 16 июл. 2021 г. в 13:28, Pavel Tupitsyn <pt...@apache.org>:
> Igniters,
>
> I was asked a few times about Data Structures [1] in thin clients.
>
> While there are plans to add them eventually, it is possible to implement
> them on top of the existing thin client cache API.
> I'd like to share a short blog post which demonstrates this [2].
>
> [1] https://ignite.apache.org/features/datastructures.html
> [2]
> https://ptupitsyn.github.io/Ignite-Thin-Client-Distributed-Blocking-Queue/
>
--
Sincerely yours, Ivan Daschinskiy