JBoss Enterprise Application Server 5 vs. IBM WebSphere Application Server 8

Re-Blogged from Howtojboss.com

JBoss Enterprise Application Platform 5 (JBoss EAP) and IBM WebSphere Application Server 8 (WAS) are both enterprise-class application servers. This post will evaluate the total cost of acquisition (TCA) of each one based on a comparable feature set and a specific set of hardware requirements.

WebSphere is available in three primary configurations:

  • WebSphere Application Server Express (WAS Express)
  • WebSphere Application Server (WAS)
  • WebSphere Application Server Network Deployment (WAS ND)

WAS Express and WAS do NOT include session replication or advanced clustering, and are NOT meant for highly transactional applications.

WAS ExpressWASWAS ND
Session ReplicationNoNoYes
Advanced ClusteringNoNoYes
Highly Transactional ApplicationsNoNoYes

JBoss EAP includes session replication, advanced clustering, and IS meant for highly transactional applications. Therefore, WAS ND is the ONLY configuration that is comparable to JBoss EAP.

WAS NDJBoss EAPJBoss EAP Details
Session ReplicationYesYesDocumentation
Advanced Clustering &
High Availability
YesYesJNDI, EJB, JMS
Documentation
Highly Transactional ApplicationsYesYes

JBoss EAP and WAS ND both include standard enterprise-class features.

WAS NDJBoss EAPJBoss EAP Details
Java EE 5 CertifiedYesYes
Choice of Programming & Component ModelsYesYesGWT, RichFaces, Spring Framework, Apache Struts, Java EE, OSGi
Remote AdministrationYesYesRemotely Deploy Servers (Documentation) and Applications (Documentation)
Choice of OS & DatabaseYesYes
Integrated Development EnvironmentYesYesJBoss Developer Studio – Integrated Tooling & Runtime Components
24X7 Technical SupportYesYes
Lightweight
Server Runtime
YesYesModular, Extensible, Dynamic
Easy to InstallYesYes
Centralized ManagementYesYesManage Server & Application Configurations
Documentation
Deployment DirectoriesYesYesDocumentation
Security DomainsYesYesDocumentation
Security AuditingYesYesMonitor Security Domains & Web/EJB Applications
Documentation
Kerberos &
Single Sign On (SSO)
YesYesSPNEGO
Documentation

In addition, JBoss EAP and WAS ND both include advanced enterprise-class features such as intelligent load balancing while providing documentation and references.

WAS NDJBoss EAPJBoss EAP Details
Intelligent Load BalancingYesYesEJB, JMS
Documentation
DocumentationYesYesLink
Mission Critical Production DeploymentsYesYes

JON, included in the JBoss EAP managed subscription, is capable of SLA driven server provisioning. WAS ND is NOT.

WAS NDJBoss EAPBoss EAP Details
Elasticity with Dynamic ProvisioningNoYesSLA driven server provisioning with JON.

WAS ND is NOT an open source application server.

WAS NDJBoss EAP
Open SourcePartialFull

Costs

Licenses v Subscriptions

Hardware Configurations

ServersSockets / ServerCores / ProcessorTotal Cores
Config A488256
Config B448128

Intel Xeon Processor X7560

PVU / Core (IBM)PVU (IBM)64 Cores (Red Hat)WAS NDJBoss EAP
Config A120$190$40,000$5,836,800$160,000
Config B100$190$40,000$2,432,000$80,000

IBM does not sell an Intel based server that requires less than 100 PVU per core.

Infrastructure

WAS NDJBoss EAP
Management Software$0$0
Database
– Management Data
– Persistent Session State
$0$0
Hardware
– Database
– Application Server
$0$0
LDAP$0$0
Object (e.g. – POJO) Caching$0$0
JDK$0$25,992 /
$51,984
(RHEL)
Messaging$0$0
HTTP Server
– Load Balancer
– Content Caching Reverse Proxy
$0$2,500 /
$5,000
(JBoss EWS)
  • JBoss EAP and WAS ND both include management and monitoring capabilities. However, WAS ND is limited to centralized management of a single cluster. JON is not. JON provides advanced management and monitoring capabilities.
  • JBoss EAP and WAS ND do NOT require a new database to be installed. Management data and persistent session state can be stored on an existing database. Since an existing database can be used, no additional database hardware is necessary.
  • JBoss EAP and WAS ND do NOT require more or less hardware than the other to be installed.
  • JBoss EAP and WAS ND do NOT require a new LDAP directory to be installed.
  • JBoss EAP and WAS ND both include support for object (e.g. – POJO) caching.
  • WAS ND includes support for a high performance messaging product. However, JBoss EAP includes high performance messaging.
  • JBoss Enterprise Web Server (JBoss EWS) and IBM HTTP server are bothbased on Apache HTTP Server. Apache HTTP Server can be configured as a reverse proxy that supports load balancing and content caching.

Integrated Development Environment

JBoss EAP includes 25 subscriptions with support for JBoss Developer Studio for every 16 supported cores. WAS ND does NOT include support for WebSphere for Developers.

WAS NDJBoss EAP
25 Users$57,000$0

Total Cost of Acquisition

WAS ND
128 Cores
WAS ND
256 Cores
JBoss EAP
128 Cores
JBoss EAP
256 Cores
Application Server$2,432,000$5,836,800$80,000$160,000
JDK$0$0$25,992$51,984
HTTP Server$0$0$2,500$5,000
IDE$57,000$57,000$0$0
Total$2,489,000$5,893,800$108,492$216,984