The Middleware Layer Model



Email    print   
August 15, 2000 —  (Page 1 of 2)
The definition of middleware as used here would encompass any kind of software that sits between two systems and makes communication easier. Most any software will fit into this category: everything from embedded software to Java Virtual Machines. It would also include things like EAI, customer relationship management and XML, none of which is really middleware, and none of which has reduced our reliance on APIs. Java, for example, has taken the proliferation of APIs to a level Microsoft could only have dreamed of while it was cobbling together the Win32 hairball. What has happened is that all these technologies, middleware or not, have decreased our dependence on operating-system APIs.

And this, of course, is a good thing. But this leaves the question of what is middleware and why is this question important?

I believe that as we advance in distributed computing, everything but the anchor applications will be called middleware-even network protocols. And, of course, the more imprecise language is, the more difficult it is to have proper communication among technical professionals. To get networking conceptually right, in the late 1980s the OSI layered model was proposed, which enabled geeks to talk about specific layers of the network rather than just calling everything from the cabling to the applications "the network."

A similar layering needs to be provided for middleware, so we can all talk about the same thing without having to define terms each time. I propose a model, for which I actively solicit comments.

The physical layer remains the same except that the advent of wireless may require us to rename it someday. I collapse the data link into the physical layer. While not strictly physical, the choices at the data link and physical layers are often interrelated.

Layer 2 is the network layer. IP, for example, would be a layer 2 protocol.

Layer 3 is a transport layer. In common parlance, the transport layer includes TCP and UDP. In the middleware layered model, it would include any other transports, including proprietary transports, used by vendors to move messages and data over the network.




Pages 1 2 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Layer 7 offers ESB appliance
Performance and maintaining a steady grasp on data flowing in and out of Oracle databases is the main priority of this tool 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