Since I'm now the Development Manager for JBossESB (amongst my roles), I'm obviously interested in things such as JBI and SCA and how they might relate. So I've been collecting articles.
Here's a nice discussion by Edwin Khodabakchian. Another by JJ (BTW, congratulations on the more to SAP JJ).
Obviously both Oracle and SAP are co-authors on SCA, so for those people who thing the above articles may not be 100% objective, there's an interesting one here, that makes a stronger statement concerning the overlap between JBI and SCA.
There are some Gartner comments here and here.
And finally one analysts take on a fairly obvious missing co-author, with which I agree.
Any more, please post to the comments.
I work for Red Hat, where I lead JBoss technical direction and research/development. Prior to this I was SOA Technical Development Manager and Director of Standards. I was Chief Architect and co-founder at Arjuna Technologies, an HP spin-off (where I was a Distinguished Engineer). I've been working in the area of reliable distributed systems since the mid-80's. My PhD was on fault-tolerant distributed systems, replication and transactions. I'm also a Professor at Newcastle University and Lyon.
Friday, December 16, 2005
Monday, December 05, 2005
Why JBoss?
So why have I moved across to JBoss? Well it hasn't been an easy choice, as quite a few people out there will know. Firstly I was one of the founders of the company. I was also a director of Arjuna Technologies and being a director of any company imposes certain obligations on you that don't come with normal employment contracts. I want Arjuna Technologies to succeed, because I believe in what we've been trying to do and also for the many shareholders who have supported us over the years.
We've been working on having a closer relationship between Arjuna Technologies and JBoss almost from the start. The fact that Bob Bickel is on our advisory board and also works for JBoss is a happy coincidence (we like to point out that Bob joined us first!) When the opportunity finally arose, it was simply too good for the company to pass up. Also to be honest, the way open source has burst onto the software scene, if the likes of IBM are feeling the pinch then you can bet that either every other middleware vendor is too, or is feeling OSS breathing down their necks! Nuff said.
The way JBoss operates when getting involved with any project, be it cacheing or transactions, is that they need to have a critical mass of knowledge as well as the software. So, as well as the transaction software that we have developed over the past 20 years, they needed the knowledge to compliment it. And that's where I came in.
I think this is an exciting opportunity for JBoss and Arjuna. It's also an extremely important deal for both companies. Which is why I, along with many other people in Arjuna, worked hard to ensure it happened. In some ways it hasn't been an easy decision to make, but in others it was the only thing that made sense.
We've been working on having a closer relationship between Arjuna Technologies and JBoss almost from the start. The fact that Bob Bickel is on our advisory board and also works for JBoss is a happy coincidence (we like to point out that Bob joined us first!) When the opportunity finally arose, it was simply too good for the company to pass up. Also to be honest, the way open source has burst onto the software scene, if the likes of IBM are feeling the pinch then you can bet that either every other middleware vendor is too, or is feeling OSS breathing down their necks! Nuff said.
The way JBoss operates when getting involved with any project, be it cacheing or transactions, is that they need to have a critical mass of knowledge as well as the software. So, as well as the transaction software that we have developed over the past 20 years, they needed the knowledge to compliment it. And that's where I came in.
I think this is an exciting opportunity for JBoss and Arjuna. It's also an extremely important deal for both companies. Which is why I, along with many other people in Arjuna, worked hard to ensure it happened. In some ways it hasn't been an easy decision to make, but in others it was the only thing that made sense.