Are transactions useful in these use-cases?

[James Green <ja...@gmail.com>]

We have a number of routes:

from(HTTP POST).to(JMS)
from(JMS).to(SOAP Endpoint).to(JMS)
from(JMS).to(MongoDB)
from(MongoDB).to(JMS)

Hugely simplified and these are across various JAR services. Are
transactions actually useful in the above?

Actually understanding the behaviour of code routes is one challenge,
understanding with transactional management adds some cognitive overhead
which may not be necessary. I'm unsure given the use-cases we have whether
it is usual to drop them in favour of client-acking of JMS messages for
instance.

Thanks,

James

Re: Are transactions useful in these use-cases?

[Willem Jiang <wi...@gmail.com>]

There are too many resources need to be managed, I’m not sure if it is worth to put all the options into one transactions. 

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On March 10, 2015 at 5:04:14 PM, James Green (james.mk.green@gmail.com) wrote:
> We have a number of routes:
>  
> from(HTTP POST).to(JMS)
> from(JMS).to(SOAP Endpoint).to(JMS)
> from(JMS).to(MongoDB)
> from(MongoDB).to(JMS)
>  
> Hugely simplified and these are across various JAR services. Are
> transactions actually useful in the above?
>  
> Actually understanding the behaviour of code routes is one challenge,
> understanding with transactional management adds some cognitive overhead
> which may not be necessary. I'm unsure given the use-cases we have whether
> it is usual to drop them in favour of client-acking of JMS messages for
> instance.
>  
> Thanks,
>  
> James
>