The Red Hat Tech Exchange take place every year in Asia Pacific, this year is in Vietnam, Ho Chi Minh city. This year's theme is Train (gain and apply knowledge and skills), Share (best practices and experiences) and Enable (your personal and customer success). I sure had a great time there.
In the event I have share 2 sessions, the first one I did with Thomas Qvarnström, it about handling large data and how JBoss Data Grid can help. You can find the slides in my previous post.
My second session talks about the difference between BPM process and Camel route, when to use what and share my thoughts on the best practices of when to use it. The agenda of my talk :
Sometimes, building enterprise class business processes is difficult, it involves complex application integration, many requires co-work between cross functions. See how JBoss BPM suite and JBoss Fuse can do! In this talk, we are going to talk about possible architectures, go through a live demo and see how it's done.
And here is the slide:
Here are some note about the transaction, when I say BPM has no transaction, I mean the automatic transaction. In BPM the transaction boundaries are between persistence nodes, so if you have 2 human tasks in the process, your process will be automatically splits into 2 or 3 transactions. If something goes wrong, BPM engine will auto roll back all nodes between persistence node. But what was done was done, say you have already called a Java bean to deduct values from databases. Although the process will start over and redo the process again, the value of data still need to handle specifically to return to original state in all the databases. But for Fuse, it can automatically rollback as it supports transactions and XA transactions for Database and JMS. It would be a great practice if we can wrap the transaction into a specific service in Fuse and allow process to call the services. If anything goes wrong, in the transaction, it will automatically row back. And Process can then be start over again, as it will also restart by BPM engine.
I hope to see you in the event next year :)