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:[email protected]] Sent: Friday, July 16, 2021 8:59 AM To: [email protected] 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 <[email protected]<mailto:[email protected]>>: 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 <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>>: 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
