Middleware Technologies for Technical Support
About Middleware:
Middleware is Connectivity software that provides services to IT applications beyond those available from the O.S. Middleware makes it easier for IT developers to perform communication and Management of data , so they must focus on the certain purpose of their applications. Middleware provides functionality that the network and operating system API’s (Application Programming Interfaces) do not provide. Some of the advantages that middleware could provide are: - independence from network services - independence from o.s calls - scalability - Avail - reliability
Middleware Technologies Architecture
Middleware architecture is an increasingly familiar topic in the world of enterprise IT. Many businesses work on a “cloud” something that seems invisible yet allows for so much probability. But we have to know what is the importence of middleware And what are the familiar aspects of the architecture of a middleware?
What does Middleware ?
Enabling Interactions
Acting as the uniform glue that collate components in the systems
Facilitate components interactions
Dealing with heterogeneous components
Supporting Interactions
Provide support for openness Provide support for problems Provide support for system manager Promoting Context-Awareness
Modles Of Middleware :
RPC and Object-based
Rooted in the “Remote Procedure Call” paradigm
Event-based
Support a reactive context-aware model
Shared Dataspaces
Rooted on shared memory models Support sorts of “stigmergic” interactions between components
Most middleware technologies, handles objects both , shared memories, and events
And provides various services for the different types of models These model, more than “interaction models” are best known as
Types of Middleware :
1.Remote procedure call :
RPC is a client server mechanisam that allows the program to be distributed across multiple platforms RPC is also a very old technology. The first full scale implementations date back to the late 1970’s. RPC provides a means to make the invocation of a routine on a server by a client application on a different machine look like any function invocation within the client application
2. Object request broker :
The server process registers it’s service with the ORB. The client contacts the ORB asking where it can find the service (resolving the location). • ORB control machine software and vendors are no boundaries for the orb • Major functionality includes: • Communication between users and objects • Location and activation
3. Transcation processing monitor :
TP monitor technology is not a new idea. This model has been used for many years in areas such as data management, network access, and customer service, to name a few. This is your basic three tier architecture with a fancy name within the context frame of middleware.
• Control transcation applications • Provide business logic,rules • Data base updates
4. Message oriented middleware
MOM architecture has one-upped RPC by providing a queuing mechanism. This is simply a means to accomplish asynchronous communication by saving messages for target nodes when they are busy, slow, or even dead.
• Functionality similar to rpc • Provides asynchronous communication b/w client and server applications by queueing messages temporarily when one or the other is busy or not connected
Tell others about
this page:
Comments? Questions? Email Here