Evans,
If you need to atomically update multiple counters, then you indeed need
locks or transaction. If both are applicable, I would recommend using
transactions.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-fine-grained-policy-quota
e in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-fine-grained-policy-quota-control-tp10563p10584.html
>
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
Hi Evans,
It sounds like you can simply use AtomicLong:
https://apacheignite.readme.io/docs/atomic-types
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-fine-grained-policy-quota-control-tp10563p10584.html
Sent from the Apache Ignite Users
Hi Igniters,
We recently are using Ignite building a real-time notification system.
Ignite plays a crucial part on policy control for notifications. For
example, we would like a user who has a quota of 100 notifications per day
gets 100 messages per day precisely. Once quota exceeded, Further
