camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: About Stream Caching
Date Mon, 07 Mar 2016 15:56:18 GMT
Well, for the rapid burst of messages, I'd probably work on tuning how many
concurrent consumers are used for that endpoint. If you need to transfer
them really fast for further processing, you could use the seda component
or camel-disruptor if you want to use a 3rd party library with it.

For the reliable messaging, I'd stick to a message broker if possible like
ActiveMQ. Unless you mean the SOAP feature in which case CXF supports that
(reliable messaging).

On 7 March 2016 at 09:33, Goyal, Arpit <arpit.goyal@sap.com> wrote:

> Hi Matt,
>
> That was my initial gut feeling. Do you have any additional details of how
> to handle such use cases?
>
> Are they dependent on the container in which Camel is running and for
> Reliable Delivery of message we have to build DB/In-memory repositories?
>
> Regards,
> Arpit.
>
> -----Original Message-----
> From: Matt Sicker [mailto:boards@gmail.com]
> Sent: Sunday, March 6, 2016 9:52 AM
> To: users@camel.apache.org
> Subject: Re: About Stream Caching
>
> Stream caching is for when the body of a message is a stream and you want
> to read from it multiple times (e.g., to log the body or run multiple
> expressions against it). I don't think it applies to either scenario.
>
> On 5 March 2016 at 13:41, Goyal, Arpit <arpit.goyal@sap.com> wrote:
>
> > Was reading about the http://camel.apache.org/stream-caching.html
> > functionality of Camel and would like to know would this also helps in
> > following use-cases:
> >
> >
> > -          There are like 1 Million (less than 5kb) messages following in
> > short duration (like 1-10 minutes)?
> >
> > -          Reliable delivery of message.
> >
> > In case this is not the right approach, could someone share approach to
> > achieve both? Any pointers would be great.
> >
> > Regards,
> > Arpit.
> >
>
>
>
> --
> Matt Sicker <boards@gmail.com>
>



-- 
Matt Sicker <boards@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message