Do we really need this? Maybe a nice to have (and to tick all boxes), but have not really
seen demand for this.
Begin forwarded message:
From: Guillermo GARCIA OCHOA <do-not-reply(a)jboss.com>
Subject: [Infinispan] - Re: Global/Normalized timestamp generator
Date: July 11, 2012 10:57:38 AM GMT+03:00
To: Galder Zamarreño <galder.zamarreno(a)redhat.com>
JBoss Community
Re: Global/Normalized timestamp generator
created by Guillermo GARCIA OCHOA in Infinispan - View the full discussion
I strongly disagree with you ...
A cluster should have a normalized timestamps generator for many use cases.
One example
Message producer/consumer: Almost all the implementations of this kind of patterns needs
a normalized timestamps to know the order of processing of the distributed queue (this
means several share-nothing queues).
One real case scenario:
Transaction processor: you have several servers handling business transactions, but to be
faster do you not centralize all these transaction in the same queue, but in several ones.
Then you can consume those queues to really process this sorted by 'creation
timestamps'.
I know there is a lot of way to do this, but timestamps are widely used in distributed
environments. Please check this:
A plugin for ActiveMQ
http://activemq.apache.org/timestampplugin.html
In Oracle Coherence you can get this normalized timestamps with
CacheFactory.ensureCluster().getTimeMillis()
Dont you think that this is important enough to be added to the roadmap? Is not blocker,
but I think that this is a 'must have' feature.
Reply to this message by going to Community
Start a new discussion in Infinispan at Community
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache