Middleware (distributed applications): Difference between revisions

Content deleted Content added

Inline

Revision as of 18:14, 27 August 2010

Middleware is computer software that connects software components or some people and their applications. The software consists of a set of services that allows multiple processes running on one or more machines to interact. This technology evolved to provide for interoperability in support of the move to coherent distributed architectures, which are most often used to support and simplify complex distributed applications. It includes web servers, application servers, and similar tools that support application development and delivery. Middleware is especially integral to modern information technology based on XML, SOAP, Web services, and service-oriented architecture.

Middleware sits "in the middle" between application software that may be working on different operating systems. It is similar to the middle layer of a three-tier single system architecture, except that it is stretched across multiple systems or applications. Examples include EAI software, telecommunications software, transaction monitors, and messaging-and-queueing software.

The distinction between operating system and middleware functionality is, to some extent, arbitrary. While core kernel functionality can only be provided by the operating system itself, some functionality previously provided by separately sold middleware is now integrated in operating systems. A typical example is the TCP/IP stack for telecommunications, nowadays included in virtually every operating system.

In simulation technology, middleware is generally used in the context of the high level architecture (HLA) that applies to many distributed simulations. It is a layer of software that lies between the application code and the run-time infrastructure. Middleware generally consists of a library of functions, and enables a number of applications–simulations or federates in HLA terminology—to page these functions from the common library rather than re-create them for each application

Definitions

Software that provides a link between separate software applications. Middleware is sometimes called plumbing because it connects two applications and passes data between them. Middleware allows data contained in one database to be accessed through another. This definition would fit enterprise application integration and data integration software.

ObjectWeb defines middleware as: "The software layer that lies between the operating system and applications on each side of a distributed computing system in a network."^[1] Middleware is a computer software that connects software components or applications. The software consists of a set of services that allows multiple processes running on one or more machines to interact. This technology evolved to provide for interoperability in support of the move to coherent distributed architectures, which are most often used to support and simplify complex, distributed applications. It includes web servers, application servers, and similar tools that support application development and delivery. Middleware is especially integral to modern information technology based on XML, SOAP, Web services, and service-oriented architecture.

In simulation technology, middleware is generally used in the context of the high level architecture (HLA) that applies to many distributed simulations. It is a layer of software that lies between the application code and the run-time infrastructure. Middleware generally consists of a library of functions, and enables a number of applications—simulations or federates in HLA terminology—to page these functions from the common library rather than re-create them for each application

Origins

Middleware is a relatively new addition to the computing landscape. It gained popularity in the 1980s as a solution to the problem of how to link newer applications to older legacy systems, although the term had been in use since 1968.^[2] It also facilitated distributed processing, the connection of multiple applications to create a larger application, usually over a network.

Organizations

IBM, Red Hat, and Oracle Corporation are major vendors providing middleware software. Vendors such as Axway, SAP, TIBCO, Informatica, Pervasive and webMethods were specifically founded to provide Web-oriented middleware tools. Groups such as the Apache Software Foundation, OpenSAF and the ObjectWeb Consortium encourage the development of open source middleware. Microsoft .NET “Framework” architecture is essentially “Middleware” with typical middleware functions distributed between the various products, with most inter-computer interaction by industry standards, open APIs or RAND software licence.

Use of middleware

Middleware services provide a more functional set of application programming interfaces to allow an application to:

Locate transparently across the network, thus providing interaction with another service or application
Filter data to make them friendly usable or public via anonymization process for privacy protection (for example)
Be independent from network services
Be reliable and always available
Add complementary attributes like semantics

when compared to the operating system and network services.

Middleware offers some unique technological advantages for business and industry. For example, traditional database systems are usually deployed in closed environments where users access the system only via a restricted network or intranet (e.g., an enterprise’s internal network). With the phenomenal growth of the World Wide Web, users can access virtually any database for which they have proper access rights from anywhere in the world. Middleware addresses the problem of varying levels of interoperability among different database structures. Middleware facilitates transparent access to legacy database management systems (DBMSs) or applications via a web server without regard to database-specific characteristics ^[3].

Businesses frequently use middleware applications to link information from departmental databases, such as payroll, sales, and accounting, or databases housed in multiple geographic locations ^[4]. In the highly competitive healthcare community, laboratories make extensive use of middleware applications for data mining, laboratory information system (LIS) backup, and to combine systems during hospital mergers. Middleware helps bridge the gap between separate LISs in a newly formed healthcare network following a hospital buyout ^[5].

Wireless networking developers can use middleware to meet the challenges associated with wireless sensor network (WSN), or WSN technologies. Implementing a middleware application allows WSN developers to integrate operating systems and hardware with the wide variety of various applications that are currently available ^[6].

Middleware can help software developers avoid having to write application programming interfaces (API) for every control program, by serving as an independent programming interface for their applications. For Future Internet network operation through traffic monitoring in multi-domain scenarios, using mediator tools (middleware) is a powerful help since they allow operators, searchers and service providers to supervise Quality of service and analyse eventual failures in telecommunication services.^[7]

Finally, e-commerce uses middleware to assist in handling rapid and secure transactions over many different types of computer environments ^[8]. In short, middleware has become a critical element across a broad range of industries, thanks to its ability to bring together resources across dissimilar networks or computing platforms.

In 2004 members of the European Broadcasting Union (EBU) carried out a study of Middleware with respect to system integration in broadcast environments. This involved system design engineering experts from 10 major European broadcasters working over a 12 month period to understand the effect of predominantly software based products to media production and broadcasting system design techniques. The resulting reports Tech 3300 and Tech 3300s were published and are freely available from the EBU web site.^[9]^[10]

Types of middleware

Hurwitz's classification system organizes the many types of middleware that are currently available.^[11]. These classifications are based on scalability and recoverability:

Remote Procedure Call — Client makes calls to procedures running on remote systems. Can be asynchronous or synchronous.
Message Oriented Middleware — Messages sent to the client are collected and stored until they are acted upon, while the client continues with other processing.
Object Request Broker — This type of middleware makes it possible for applications to send objects and request services in an object-oriented system.
SQL-oriented Data Access — middleware between applications and database servers.
Embedded Middleware — communication services and integration interface software/firmware that operates between embedded applications and the real time operating system.

Other sources include these additional classifications:

Transaction processing monitors — Provides tools and an environment to develop and deploy distributed applications.
Application servers — software installed on a computer to facilitate the serving (running) of other applications.
Enterprise Service Bus — An abstraction layer on top of an Enterprise Messaging System.

References

^ Krakowiak, Sacha. "What's middleware?". ObjectWeb.org. Retrieved 2005-05-06.
^ Gall, Nick (July 30, 2005). "Origin of the term middleware".
^ Peng, C, Chen, S, Chung, J, Roy-Chowdhury, A, and Srinivasan, V. (1998). Accessing existing business data from the World Wide Web. IBM Systems Journal, 37(1), 115-132. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 26217517)
^ Bougettaya, A, Malik, Z, Rezgui, A, and Korff, L. (2006). A Scalable Middleware for Web Databases. Journal of Database Management, 17(4), 20-39,41-46. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 1155773301).
^ Bagwell, H. (2008). Middleware: providing value beyond autoverification^{[dead link]}. IVDT. Retrieved March 3, 2009.
^ Hadim, S. and Mohamed, N. (2006). Middleware challenges and approaches for wireless sensor networks. IEEE Distributed Systems Online vol 7. Issue 3. Retrieved March 4, 2009 from iEEE Distributed Systems Online
^ Kai Oswald Seidler. "MOMENT". Fp7-moment.eu. Retrieved 2010-08-19.
^ Charles, J. (1999). Middleware moves to the forefront(subscription required). Technology News. Retrieved March 2, 2009.
^ "EBU middleware report Tech 3300" (PDF). Retrieved 2010-08-19.
^ "EBU middleware reports Tech 3300s" (PDF). Retrieved 2010-08-19.
^ Hurwitz, Judith (January, 1998). "Sorting Out Middleware". DBMS 11.1. Archived from the original on 2006-10-17. Retrieved 2009-01-20. {{cite web}}: Check date values in: |date= (help)

External links

[1] Krakowiak, Sacha. "What's middleware?". ObjectWeb.org. Retrieved 2005-05-06.

[2] Gall, Nick (July 30, 2005). "Origin of the term middleware".

[3] Peng, C, Chen, S, Chung, J, Roy-Chowdhury, A, and Srinivasan, V. (1998). Accessing existing business data from the World Wide Web. IBM Systems Journal, 37(1), 115-132. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 26217517)

[4] Bougettaya, A, Malik, Z, Rezgui, A, and Korff, L. (2006). A Scalable Middleware for Web Databases. Journal of Database Management, 17(4), 20-39,41-46. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 1155773301).

[5] Bagwell, H. (2008). Middleware: providing value beyond autoverification^{[dead link]}. IVDT. Retrieved March 3, 2009.

[6] Hadim, S. and Mohamed, N. (2006). Middleware challenges and approaches for wireless sensor networks. IEEE Distributed Systems Online vol 7. Issue 3. Retrieved March 4, 2009 from iEEE Distributed Systems Online

[7] Kai Oswald Seidler. "MOMENT". Fp7-moment.eu. Retrieved 2010-08-19.

[8] Charles, J. (1999). Middleware moves to the forefront(subscription required). Technology News. Retrieved March 2, 2009.

[9] "EBU middleware report Tech 3300" (PDF). Retrieved 2010-08-19.

[10] "EBU middleware reports Tech 3300s" (PDF). Retrieved 2010-08-19.

[11] Hurwitz, Judith (January, 1998). "Sorting Out Middleware". DBMS 11.1. Archived from the original on 2006-10-17. Retrieved 2009-01-20. {{cite web}}: Check date values in: |date= (help)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

@@ Line 1: / Line 1: @@
 {{About|integration software|video game engine software|Game engine#Middleware}}
-'''Middleware''' is [[computer]] [[software]] that connects [bvnbvn[software component]]s or some people and their applications.  The software consists of a set of services that allows multiple processes running on one or more machines to interact. This technology evolved to provide for [[interoperability]] in support of the move to coherent distributed architectures, which are most often used to support and simplify complex [[distributed application]]s. It includes [[web server]]s, [[application server]]s,  and similar tools that support application development and delivery.  Middleware is especially integral to modern information technology based on [[XML]], [[SOAP]], [[Web service]]s, and [[service-oriented architecture]].
+'''Middleware''' is [[computer]] [[software]] that connects [[software component]]s or some people and their applications.  The software consists of a set of services that allows multiple processes running on one or more machines to interact. This technology evolved to provide for [[interoperability]] in support of the move to coherent distributed architectures, which are most often used to support and simplify complex [[distributed application]]s. It includes [[web server]]s, [[application server]]s,  and similar tools that support application development and delivery.  Middleware is especially integral to modern information technology based on [[XML]], [[SOAP]], [[Web service]]s, and [[service-oriented architecture]].
 Middleware sits "in the middle" between [[application software]] that may be working on different [[operating system]]s. It is similar to the middle layer of a [[Multitier architecture|three-tier]] single system architecture, except that it is stretched across multiple systems or applications. Examples include [[Enterprise Application Integration|EAI]] software, telecommunications software, [[Transaction Processing System|transaction monitors]], and messaging-and-queueing software.