On Mon, May 7, 2018 at 8:10 AM, pragmaticjdev wrote:
> I think there is some misunderstanding that I created. We don't plan to use
> activemq to populate the cache. We build the cache on cache misses. Here's
> how the overall flow looks like. Note there are multiple jvm's involved, I
> have just
I think there is some misunderstanding that I created. We don't plan to use
activemq to populate the cache. We build the cache on cache misses. Here's
how the overall flow looks like. Note there are multiple jvm's involved, I
have just pictured one for simplicity.
I didn't completely follow your r
On Wed, May 2, 2018, 12:02 AM pragmaticjdev wrote:
> Thanks Tim for your valuable comments.
>
> 1.
>
> > so you're using message-driven code rather than managing the connection
> > yourself. In that case you'd want to do the following to handle the
> error
> > (by clearing the cache):
> >
> https
Thanks Tim for your valuable comments.
1.
> so you're using message-driven code rather than managing the connection
> yourself. In that case you'd want to do the following to handle the error
> (by clearing the cache):
> https://stackoverflow.com/questions/40654586/spring-jms-set-errorhandler
Oh, one other thing. @JmsListener is typically used with a
DefaultMessageListenerContainer, which interacts poorly with topics if the
subscription is non-durable because the DMLC typically disconnects and
reconnects for every message, allowing messages to be "lost" for
non-durable subscriptions. Se
On Mon, Apr 23, 2018 at 11:48 PM, pragmaticjdev wrote:
> Highly appreciate the detailed replies and the clarifications on
> distributed
> cache vs database.
> We are trying to build a distributed cache. I agree to all the inputs you
> shared for such a cache implementation. In summary it would me
Any thoughts on how to control the polling interval and other queries
mentioned below?
Thanks!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Highly appreciate the detailed replies and the clarifications on distributed
cache vs database.
We are trying to build a distributed cache. I agree to all the inputs you
shared for such a cache implementation. In summary it would mean
1. Subscriber should clear the cache when it cannot conn
I think you need to figure out whether you're trying to build a distributed
cache or a distributed database, because right now you seem to be trying to
build something halfway between the two and it's leading to an inconsistent
set of requirements.
If you're trying to build a distributed cache, th
Thanks for the replies.
Below are my comments on the discussed topics
> Have you considered using an actual standalone caching product such as
> Redis or MemCache as your cache rather than trying to create your own
> synchronized distributed in-memory cache?
That was the first thought but sinc
I wouldn't say it's atomic, it just shifts around some of the error cases
(you risk reading uncommitted writes that might be rolled back, instead of
risking having a cache miss when a value should exist).
In general, the terms "atomic" and "distributed" are contradictory in most
situations. If the
Apache Ignite (is ASF product in this space)
Saying that if you want to do this, and not have consistency issue, if you
design it so you publish the change event into the topic first and your app
(including the instance that produces) consumes the data to update their local
cache .
This way t
I agree with Tim about using an existing cache implementation. It seems
like a lot of work to re-invent the wheel here. If you're looking for an
open-source, Java-based cache implementation which uses the ASL 2.0 (e.g.
similar to Apache ActiveMQ) checkout in Infinispan [1].
Justin
[1] http://inf
On Wed, Apr 11, 2018, 6:09 AM pragmaticjdev wrote:
> We plan to use activemq to build a replicated cache in our distributed
> system
> consisting of multiple java applications. In this deployment, an update to
> any of the objects being cached in the jvm memory of the app server acts as
> a produ
14 matches
Mail list logo
