The last day of Devoxx. For me every session of this conference has been worthwhile. I am very glad I was there. On the last day I attended a session presented by Paul Brown. He was talking about BPM in a SOA environment. After that a session about slicing up web applications into vertical slices. It was interesting for me because I am looking for this kind of separation for a while, but I never found a good way to do it. The last session (Fuse) was like a University session: great explanation with some good code examples.
Paul Brown: BPM in a SOA Environment
In a service-oriented architecture a BPM engine is both a provider and consumer of services. BPM’s consumed services generally provide access to the enterprise’s applications, while its provided services define and manage business processes. These provided services are used by different types of interfaces and other services. An architect should think through intended utilization. Also he should design for failure. And above all, think total architecture: business purpose, business processes, people, information, system. Pay attention to user interaction styles; changes in style may impact many layers.
After the talk Mr. Brown signed my copy of ‘Succeeding with SOA; Realizing Business Value Through Total Architecture’.
Andy Wilkinson: Modular Web Applications with OSGi
Spring Dynamic Modules enables building modular web applications: splitting the libraries from the web application. OSGi gives the ability to dynamically add, remove, and replace functionality at runtime. SpringSource Slices goes even further. Using the Spring Source Slices libraries it is possible to slice a web application vertically. This means that different parts of one web application can be developed in separate teams. This is great. At this moment Slices is still tied to OSGi. Soon also a standard Servlet container will be available. This means that potentially this functionality can be applied to many web frameworks.
James Strachan: Open Source SOA with Fuse
Fuse is a supported distribution of popular Apache SOA and integration projects: ActiveMQ, CFX, ServiceMix, and Camel. ActiveMQ offers messaging. Messaging is like e-mail between a applications. ActiveMQ offers reliable load balancing and high performance. CFX consumes web services. ServiceMix is a container for integration glue. Camel is a library that offers a way to use the Enterprise Integration Patterns in an easy way. For example the MessageFilter. Camels offers the ability to describe routes in every programming language you like; XML, Java, Scala, Ruby, Groovy, etc. The code examples during the presentation showed that Camel API is very easy to use.