Middleware (distributed applications)

Middleware in the context of distributed applications is software that provides services beyond those provided by the operating system to enable the various components of a distributed system to communicate and manage data. Middleware supports and simplifies complex distributed applications. It includes web servers, application servers, messaging 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.

This article is about distributed applications. For middleware in general, see Middleware.

Middleware often enables interoperability between applications that run on different operating systems, by supplying services so the application can exchange data in a standards-based way. 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.

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]

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.

Use

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]

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.[6]

Finally, e-commerce uses middleware to assist in handling rapid and secure transactions over many different types of computer environments.[7] 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.[8][9]

Types

Message-oriented middleware

Message-oriented middleware (MOM) [10] is middleware where transactions or event notifications are delivered between disparate systems or components by way of messages, often via an enterprise messaging system. With MOM, messages sent to the client are collected and stored until they are acted upon, while the client continues with other processing.

Enterprise messaging
An enterprise messaging system is a type of middleware that facilitates message passing between disparate systems or components in standard formats, often using XML, SOAP or web services. As part of an enterprise messaging system, message broker software may queue, duplicate, translate and deliver messages to disparate systems or components in a messaging system.
Enterprise service bus
Enterprise service bus (ESB) is defined by the Burton Group [11] as "some type of integration middleware product that supports both message-oriented middleware and Web services".

Intelligent middleware

[12] Intelligent Middleware (IMW) provides real-time intelligence and event management through intelligent agents. The IMW manages the real-time processing of high volume sensor signals and turns these signals into intelligent and actionable business information. The actionable information is then delivered in end-user power dashboards to individual users or is pushed to systems within or outside the enterprise. It is able to support various heterogeneous types of hardware and software and provides an API for interfacing with external systems. It should have a highly scalable, distributed architecture which embeds intelligence throughout the network to transform raw data systematically into actionable and relevant knowledge. It can also be packaged with tools to view and manage operations and build advanced network applications most effectively.

Content-centric middleware

Content-centric middleware offers a simple provider-consumer abstraction through which applications can issue requests for uniquely identified content, without worrying about where or how it is obtained. Juno is one example, which allows applications to generate content requests associated with high-level delivery requirements.[13] The middleware then adapts the underlying delivery to access the content from sources that are best suited to matching the requirements. This is therefore similar to Publish/subscribe middleware, as well as the Content-centric networking paradigm.

Remote procedure call
Remote procedure call middleware enables a client to use services running on remote systems. The process can be synchronous or asynchronous.
Object request broker
With object request broker middleware, it is possible for applications to send objects and request services in an object-oriented system.
SQL-oriented data access
SQL-oriented Data Access is middleware between applications and database servers.
Embedded middleware
Embedded middleware provides communication services and software/firmware integration interface that operates between embedded applications, the embedded operating system, and external applications.

Other

Other sources include these additional classifications:

  • Transaction processing monitors – provides tools and an environment to develop and deploy distributed applications.[14]
  • Application servers – software installed on a computer to facilitate the serving (running) of other applications.[15]

Integration Levels

Data Integration
  • Integration of data resources like files and databases

Cloud Integration
  • Integration between various cloud services

B2B Integration
  • Integration of data resources and partner interfaces

Application Integration
  • Integration of applications managed by a company

Vendors

IBM, Red Hat, Oracle Corporation and Microsoft are some of the vendors that provide middleware software. Vendors such as Axway, SAP, TIBCO, Informatica, Objective Interface Systems, Pervasive, ScaleOut Software and webMethods were specifically founded to provide more niche middleware solutions. Groups such as the Apache Software Foundation, OpenSAF, the ObjectWeb Consortium (now OW2) and OASIS' AMQP 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. Solace provides middleware in purpose-built hardware for implementations that may experience scale. StormMQ provides Message Oriented Middleware as a service.

gollark: You can partition them, not sure about manually.
gollark: Wait, you mean *manually* move them through those, or what?
gollark: Makes sense. Trouble is, though, even if I know which items should go where, how do I move them without huge buffers?
gollark: I have a bunch of pre-set-up storage barrel thingies and just want the stuff stored in cells to be efficiently stored.
gollark: I found *one* but I have no idea how it works.

See also

References
  1. Krakowiak, Sacha. "What's middleware?". ObjectWeb.org. Archived from the original on 2005-05-07. Retrieved 2005-05-06.
  2. Gall, Nick (July 30, 2005). "Origin of the term '".
  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 Archived 2009-10-12 at the Wayback Machine. IVDT. Retrieved March 3, 2009. "Archived copy". Archived from the original on 2009-10-12. Retrieved 2009-03-09.CS1 maint: archived copy as title (link).
  6. Kai Oswald Seidler. "MOMENT". Fp7-moment.eu. Retrieved 2010-08-19.
  7. Charles, J. (1999). Middleware moves to the forefront (subscription required). Technology News. Retrieved March 2, 2009.
  8. "EBU middleware report Tech 3300" (PDF). Retrieved 2010-08-19.
  9. "EBU middleware reports Tech 3300s" (PDF). Retrieved 2010-08-19.
  10. Curry, Edward. 2004. "Message-Oriented Middleware" . In Middleware for Communications, ed. Qusay H Mahmoud, 1-28. Chichester, England: John Wiley and Sons. doi:10.1002/0470862084.ch1. ISBN 978-0-470-86206-3
  11. "Microsoft on the Enterprise Service Bus (ESB)". August 2005. The ESB label simply implies that a product is some type of integration middleware product that supports both MOM and Web services protocols.
  12. Choosing the Right Middleware Archived 2012-04-02 at the Wayback Machine "Archived copy" (PDF). Archived from the original (PDF) on 2012-04-02. Retrieved 2011-09-15.CS1 maint: archived copy as title (link)
  13. Juno Archived 2011-04-26 at the Wayback Machine "Archived copy" (PDF). Archived from the original (PDF) on 2011-04-26. Retrieved 2011-03-12.CS1 maint: archived copy as title (link), Gareth Tyson, A Middleware Approach to Building Content-Centric Applications. PhD Thesis, Lancaster University (2010).
  14. Gerndt, Michael (2002). Performance-Oriented Application Development for Distributed Architectures: Perspectives for Commercial and Scientific Environments. IOS PR, Inc. ISBN 978-1586032678.
  15. Dong, Jielin (2007). Network Dictionary. Javvin Press. ISBN 978-1602670006.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.