ProductsDesktop Server OpenStack Platform For IBM POWER For IBM System z For SAP Business Applications Satellite Management For Scientific ComputingExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportAccelerate Automate Integrate Red Hat JBoss BPM Suite Developer Studio Portfolio Edition Web Framework Kit Application Platform Web Server Data Grid Portal A-MQ Fuse BRMS Fuse Service Works Operations Network JBoss Community or JBoss enterprise Red Hat JBoss Data Virtualization
SolutionsWhy Red Hat Why open hybrid cloud? The new IT Public cloud Cloud resource library Private cloud Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Cloud applications and workloadsSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release JBoss Enterprise Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum Red Hat JBoss Middleware development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingSOA and integration Business process management Cloud and virtualization Custom Software Development Enterprise Data and Storage Systems management Migrations
Software Cycles: Back to Interoperability
June 25, 2007
by JBoss Team
An excerpt from Mark Little’s blog on JBoss.com:
The software industry goes through cycles in just the same way as other industries. Back in the early 1980s, we were working on defining distributed systems with work on RPC, stub generators, naming services, transactions, security etc. A lot of work was done by vendors and academia. Interoperability or portability were not considered important.
In the 1990s, we started to look at interoperability through CORBA (portability was still mostly a nice-to-have until the end of the century). When Java and J2EE came on the scene, portability took center stage and interoperability between heterogeneous implementations dropped away unless you wanted to embed a CORBA ORB in your application server. Now we’re into the Web Services age and interoperability is king. Portability has nothing to do with Web Services specifications or standards bodies. That’s the domain of implementation and other organizations such as JCP. It can often be a strange and inefficient approach. At least with CORBA you eventually got interoperability between different implementations, languages and portability in the same package. With Web Services, you get interoperability out-of-the-box as soon as you implement (assuming you conform to the specifications and understand what they say, or don’t say). But portability may not come for months or years!
Red Hat/JBoss is heavily into portability, interoperability and standards compliance. Over the past years, we’ve been looking out for any opportunities to help out customers in these areas: joining the Interoperability Vendor Alliance, participating in a range of Web Services events, and working on standards committees such as WS-BPEL, WS-TX, WS-Addressing and WS-Policy. Standards compliance is critically important for us and our customers: we want to avoid a return to the bad days of vendor lock-in. We take interoperability as a must when developing our products. When it’s treated as a second thought, it’s often difficult to retro-fit for existing customers. Portability is a given because of our strong support for JEE.
See the remainder of the blog here.