What is the TCO difference between IBM WebSphere and Open Source JBoss? – Just my two cents…

Disclaimer: I work for an “open source company”. The following is my personal opinion!

Great Article: “What is the TCO difference between WebSphere and JBoss?”

I have spotted a really great article about comparing prices of open source and proprietary products: “What is the TCO difference between WebSphere and JBoss?“. The interesting aspect is, that this article is written by an IBM-biased company (Prolifics). Usually, only open source vendors write such comparisons. I really like this article, seriously! It is good to see comparisons not only by open source vendors, but also by vendors such as IBM (in this case, Prolifics cannot be considered unbiased, it is an IBM consulting company – but that is fine). I just want to give my two cents to this article in the following…

Features, Performance, Availability?

I definitely agree that proprietary vendors have more features, best performance, and highest availability. So, if I have got a 100 million dollar project, where I need all of these features, and where I have to deploy to 1000s of servers, then IBM (or Oracle or SAG or XYZ) might be a good choice! However, in probably 95 percent of use cases, you do not need ALL features, BEST performance, and HIGHEST availability. You just need to solve your problem! Think about this before deciding for a whole stack of proprietary products.

Regarding some other aspects: I disagree that proprietary products have got better manageability and ease of use.

Manageability?

Production-ready installations for open source products can be done within one day – without a lot of expensive consulting efforts. You cannot install the production-ready Websphere stack in one or two days! It is much more complex. Maybe you can make it to install the development edition in one or two days on your laptop. Maybe…

And what about manageability if there is a missing feature. In an open source product, you are very flexible. You can add or change features as you want. Just change the code. That’s it. As these products usually base on open source projects (e.g. Eclipse or Apache), you find all information you need, including documentation and a large community (which helps for free). If you do not want to change it by yourself, the commercial support will help you quickly and just charge the “consulting days” of implementing the new feature. You will get a new feature in a few days or weeks (depending on its size). Try to get a new feature or a change request from proprietary vendors. Good luck. You have to pay a lot of money and / or wait a very long time!

Ease of Use?

As a developer, you can just download an open source product, use an one-click-installer, and use it. Usually, the product is an unified platform, i.e. you can do everything within the development environment intuitively. You are learning by doing. If you want to use the IBM Websphere stack, you have to install several different products. Yes, they are all “Websphere”, but nevertheless, they are different products with different tooling, based on different technologies and code bases (as many of the products come from acquisitions).

Conclusion?

So again, I really like this comparison from an IBM perspective. Every decision maker should consider both views (in the case of this article JBoss and IBM), and then decide by himself. Both solutions are good, but they differ a lot – not just in pricing! Look at all products deeply, do a proof of concept, then make a decision!

What’s your opinion? Feel free to give a comment…

 

Best regards,

Kai Wähner (Twitter: @KaiWaehner)