On Thu, Jul 30, 2015 at 2:48 PM, Raul Kripalani <[email protected]> wrote:
> Hey Dmitriy, > > Definitely. > > We have several cache components in Camel. Aside from Hazelcast there is > Ehcache, Infinispan, etc. But they act as standard endpoints. Do you think it makes sense to have a standard Ignite Cache endpoint as well? > In my opinion, the integration can be much more transparent with a bit of > imagination. > > In the caching area, ideally I would like to achieve AOP style caching like > Spring Cache, around endpoints, processors, beans, etc. > Are you suggesting to have Spring Cache endpoint so that every caching product that implements Spring Cache would automatically integrate with Camel? BTW, Ignite integrates with Spring cache: https://apacheignite.readme.io/docs/spring-caching > In the messaging area, Ignite could provide inter-container communication > between Camel routes acting like a distributed direct: endpoint. > Agree, very good suggestion. > The service grid functionality also has lots of potential. > Happy to brainstorm ideas with you. > Useful also as an Idempotency repository. > Are you talking about Camel Idempotent Consumer, similar to HazelcastIdempotentRepository? > All in all, I'm excited about all the possibilities aside from just > an ordinary component :-) > > Having said this, camel-ignite would fit better in the Camel than in the > Ignite community I believe. > I agree, Camel repository seems a better fit. However, as we get deeper, some work may potentially be needed on the Ignite side as well. Perhaps someone in the Ignite community will want to help out as well. Would you be interested in taking some of it on? Or if you would rather do some Ignite streaming work (e.g ActiveMQ), it would be very useful as well. > WDYT? > > Raúl. > On 30 Jul 2015 21:33, "Dmitriy Setrakyan" <[email protected]> wrote: > > > Hi Raul, > > > > Welcome! It's great to have a person with your qualifications join the > > Ignite community. > > > > I think given your Apache Camel involvement, integration with Camel would > > be a very useful contribution. Perhaps something like this: > > http://camel.apache.org/hazelcast-component.html ? > > > > What do you think? > > > > D. > > > > > > On Thu, Jul 30, 2015 at 12:05 PM, Raul Kripalani <[email protected]> > wrote: > > > > > Hey guys, > > > > > > I'm impressed with the technical aspects of Apache Ignite and well as > the > > > quality of the community, including all the work that surrounds the > > > development itself: docs, planning, organisation, identity and social > > media > > > presence. Great job! > > > > > > I would like to get involved in your project. > > > > > > As an integration and messaging specialist – currently a committer and > > PMC > > > member in the Apache Camel project – I can contribute to the streaming > > > block of tasks. Particularly with the Apache ActiveMQ, MQTT and Apache > > > Storm streamers. With ZeroMQ we might face some licensing challenges. > > > > > > Feel free to hit me on LinkedIn (link in my signature) to get to know > my > > > background a little more. > > > > > > Thanks for your great work so far! > > > > > > Regards, > > > > > > *Raúl Kripalani* > > > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source > > > Integration specialist > > > http://about.me/raulkripalani | > http://www.linkedin.com/in/raulkripalani > > > http://blog.raulkr.net | twitter: @raulvk > > > > > >
