We use ignite mostly as a data cache and that fits and satisfy our needs. On the other hand we store some metadata in a seperate cache, we can maybe call as "global static metadata" which have around ~100 keys on it. So every time before reaching a data cache each thread access "global static cache".
The bussiness need is checking some global constraints accross cluster before exectung some logic. What would be your suggestion ? Thanks. On Mon, Nov 28, 2016 at 11:12 PM, vkulichenko <valentin.kuliche...@gmail.com > wrote: > What's your business use case? If you have only one key, then you will > indeed > have lock-the-world on each operation, but this is very not typical use > case > for Ignite. Are you sure your approach is correct? What problem are you > trying to solve by switching to Ignite? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Blocked-get-operation-problem-tp9133p9232.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- *Tolga KAVUKÇU*
