oscerd commented on PR #22158: URL: https://github.com/apache/camel/pull/22158#issuecomment-4168968426
> ``` > # Caffeine example > camel.beans.caffeineBackend = #class:org.apache.camel.component.statestore.caffeine.CaffeineStateStoreBackend > camel.beans.caffeineBackend.maximumSize = 50000 > > # Redis example > camel.beans.redisBackend = #class:org.apache.camel.component.statestore.redis.RedisStateStoreBackend > camel.beans.redisBackend.redisUrl = redis://myhost:6379 > camel.beans.redisBackend.mapName = my-app-state > > # Infinispan example > camel.beans.infinispanBackend = #class:org.apache.camel.component.statestore.infinispan.InfinispanStateStoreBackend > camel.beans.infinispanBackend.hosts = myhost:11222 > camel.beans.infinispanBackend.cacheName = my-cache > ``` > > This sounds fine, but from a usability perspective, it would be nice to be able to reuse the existing Camel Infinispan or Redis components. This is not the first time we are "reinventing the wheel" for this kind of use case. > > Given that we already have Infinispan and Redis components with their own configurations — which are supposed to be more feature-rich than the current state store implementation — I was wondering whether we could find a way to reuse those components (or at least part of their logic) for these use cases. > > fyi @gnodet @orpiske @oscerd @apupier I'm failing to see the reason why we should have another component of this kind, it will cause another dose of entropy. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
