The State of Middleware


Java Messaging, adapters gain momentum


Email    print   
January 15, 2002 —  (Page 1 of 9)
By Andrew Binstock

Messaging middleware has undergone a stunning transformation in perception during the past five years. In the mid-1990s, middleware was still viewed very much as the province of mainframe shops that needed a plumbing layer to provide messaging between the back-room big iron and front-end applications.

This perception was furthered by the dominant role of IBM Corp.'s MQSeries middleware, which undeniably started out as a mainframe messaging layer. With the advent of Web technologies, companies discovered that the most significant impact on their enterprise infrastructure was the abrupt and radical shift to distributed architectures. The once-standard client/server model of multiple clients feeding into a business-logic server that spoke with several back-end databases was completely shattered.

In its place, a legion of dedicated, stand-alone servers took over transaction processing as a series of disjointed activities. For example, the modern enterprise with a Web presence now must support Web servers, firewalls, authentication and encryption servers, application servers, database servers and perhaps EAI servers and ERP systems. To these may well be added directory servers, WAP servers, file servers and more. The bottom line is that enterprises today are forced to deal with moving data at high speeds among a widely distributed set of servers that need to understand one another's data. Enter messaging middleware.

Suddenly, after years of rendering rock-solid service in quiet obscurity, middleware is hot and can be divided roughly into two camps: Java-based middleware and everything else.

JMS: COMING ON STRONG As of last year, the big news was the impending widespread adoption of the Java Message Service (JMS), which was expected to drive down prices as various vendors started shipping competing implementations. In addition, JMS would do away with the single biggest problem in messaging middleware: its tendency to lock customer sites into one product's API. Customers who chose one vendor's solution were locked into that product because the customers' applications all had been rewritten to use the middleware APIs. By being forced to standardize on the JMS APIs, middleware vendors would now compete purely on implementation, and dissatisfied customers could with some effort swap in a better product without having to change their codebases.




Pages 1 2 3 4 5 6 7 8 9 


Share this link: http://sdt.bz/26271
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Growth seen in application middleware
The world market for middleware grew by 13% last year, according to Gartner. Demand for service-oriented architecture and advances in middleware technology are seen as the two biggest contributors to the growth Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb