One more time this year, I will give some talks at the OW2 annual conference. I spoke about Petals and the Cloud in 2010 and 2011 and this year again, I will talk about it but not only:
Playing with SOA, EDA and Event Processing in the Cloud. I will introduce the PLAY research project which will soon become an OW2 project. (Hope to do a demo which works on low resolution this year…)
What’s new in Petals?Petals is not only an Enterprise Service Bus, there are also cool tools around which help to integrate your services and run your processes in a distributed way. We will also give details about what is coming in the next months, we have many things in mind. This will be a join talk with @VincentZurczak
Development 2.0 @ OW2. Finally, as an active Technology Council member, I will share a talk with @sauthieg and @clementplop to introduce our vision on a distributed/collaborative development platform.
Almost true… In fact Petals DSB uses and extends Petals ESB in several ways. When I started to think about extending the Enterprise Service Bus, it was just to avoid all the JBI stuff at the management level i.e. use a real, simple and efficient API. So I added many management stuff exposed as Web services : Bind external services, expose internal services (oh yes bind + expose = proxy), get endpoints, activate things, etc…
One other goal was to avoid to use closed protocols for inter node communication: The ESB uses at least three ports to create inter node communications for JMX, NIO and SOAP. So why not, just using an open protocol like SOAP and just one port? This is what I did, I changed some implementations to use the same port and the same protocol for all services.
All this stuff has been developed focusing on extensibility and easier development. This is mainly because the ESB can be hard to extend for newbies, there are so many things inside… Today the DSB is not only a Distributed Service Bus, it is also a framework so that developers can easily extend the DSB without the need to know how it works inside. Some examples? Want to expose a kernel service : Add the JAXWS @WebService annotation. Want to subscribe to Web service notifications : Annotate you Java method with @Notify. Want to be notified about new endpoints : Add the @RegistryListener annotation. That’s all, you do not have to search for the Web service server to expose your service, nor read all the WSN documentation to receive notifications, … Simple, efficient.
There are other things you can do, mostly all is detailed in the DSB page.
Comme le reste des talks proposés par la communauté OW2 à OSCON 2011, le mien a aussi été rejeté. Pourtant le titre sonnait bien « Cloud Service Bus – a public, private and hybrid cloud integration approach for SOA » .Bizarre… Serait ce parce que nous ne sommes pas sponsor de la conf, parce que nous sommes mauvais, ou pire bon mais Français? Ah non c’est le Cloud, c’est has-been. Dommage, j’avais des choses presque intéressantes à raconter, vous en pensez quoi?
The attendee will first learn how a Cloud-aware SOA software infrastructure can be built combining an Enterprise Service Bus [http://petals.ow2.org] and a Cloud infrastructure framework [http://opennebula.org]. This creates a ‘Cloud Service Bus’ which will allow the integration of in-house services in order to benefit from Cloud-based features such as elasticity, load balancing, service clustering and migration. Then, the talk will go one step further: by using the Cloud framework capabilities, the Cloud Service Bus can be extended to a hybrid approach combining both public and private Clouds. This shows the attendee how to bring the advantages of modern cloud based solutions to legacy enterprise applications while keeping sensitive data and services inside the enterprise. A Cloud-based SOA solution needs to be governed, monitored and managed in a totally transparent way akin to a traditional SOA solution; throughout the presentation the talk will show how the Cloud Service Bus approach does not break the SOA paradigm.