Computer software that provides services to software applications
Middleware is a type ofcomputer software program that provides services to software applications beyond those available from theoperating system. It can be described as "software glue".[1][2]
Middleware makes it easier forsoftware developers to implement communication and input/output, so they can focus on the specific purpose of their application. 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.[3]
The term is most commonly used for software that enables communication and management of data indistributed applications. AnIETF workshop in 2000 defined middleware as "those services found above thetransport (i.e. over TCP/IP) layer set of services but below the application environment" (i.e. below application-levelAPIs).[citation needed] In this more specific sensemiddleware can be described as the hyphen ("-") inclient-server, or the-to- inpeer-to-peer. Middleware includesweb servers,application servers,content management systems, and similar tools that support application development and delivery.[4]
Database access services are often characterised as middleware. Some of them are language specific implementations and support heterogeneous features and other related communication features.[7] Examples of database-oriented middleware includeODBC,JDBC, andtransaction processing monitors.[8]
Distributed computing system middleware can loosely be divided into two categories—those that provide human-time services (such as web request servicing) and those that perform in machine-time. This latter middleware is somewhat standardized through theService Availability Forum[9] and is commonly used in complex,embedded systems within the telecom, defence, andaerospace industries.[10]
Many categories of middleware have been defined, based on the field in which it is used or the application module it serves. A recent bibliography identified the main categories of middleware as follows:[11]
Transactional: Processing of multiple synchronous/asynchronous transactions, serving as a cluster of associated requests from distributed systems such as bank transactions or credit card payments.
Message-oriented: Message queue and message passing architectures that support synchronous/asynchronous communication.
Procedural: Remote and local architectures to connect, pass, and retrieve software responses of asynchronous systems communications such as a call operation.
Object-oriented: Similar to procedural middleware, but incorporates object-oriented programming design principles. Analytically, its software component encompasses object references, exceptions, and inheritance of properties via distributed object requests.
The termmiddleware is used in other contexts as well.Middleware is sometimes used in a similar sense to asoftware driver, an abstraction layer that hides detail about hardware devices or other software from an application.
TheAndroid operating system uses theLinux kernel at its core, and provides anapplication framework that developers incorporate into their applications. In addition,Android provides a middleware layer includinglibraries that provide services such as data storage, screen display,multimedia, and web browsing. Because the middleware libraries arecompiled tomachine language, services execute quickly. Middleware libraries also implement device-specific functions, so applications and the application framework need not concern themselves with variations between Android devices. Android's middleware layer also contains theARTvirtual machine and its coreJava application libraries.[12]
Middleware also refers to the software that separates two or more APIs and provides services such as rate-limiting, authentication, and logging.
Game engine software such asGamebryo andRenderWare are sometimes described as middleware because they provide services to simplify game development.[13]
In simulation technology,middleware is generally used in the context of thehigh level architecture (HLA) that applies to many distributed simulations. It is a layer of software that lies between theapplication code and therun-time infrastructure. Middleware generally consists of a library of functions, and enables a number of applications—simulations or federates in HLA terminology—topage these functions from the common library rather than recreate them for each application.[14]
Wireless networking developers can use middleware to meet the challenges associated with awireless sensor network (WSN). Implementing a middleware application allows WSN developers to integrate operating systems and hardware with the wide variety of currently available applications.[15]
TheQNX operating system offers middleware for providing multimedia services for use inautomobiles,aircraft, and other environments.[16]
^"Middleware conference".middleware-conf.github.io. Retrieved2023-12-16.Middleware is a distributed-system software that resides between applications and underlying platforms (operating systems; databases; hardware), and/or ties together distributed applications, databases or devices. Its primary role is to coordinate and enable communication between different layers or components while isolating much of the complexity of distribution into a single, well tested and well understood system abstraction.
^"What is Middleware?".Middleware.org. Defining Technology. 2008. Archived from the original on June 29, 2012. Retrieved2013-08-11.
^Charlie Collins, Michael Galpin and Matthias Kaeppler, Android in Practice, Manning Publications, 2011
^Moore, M. E. (2006).Introduction to the Game Industry. Pearson Prentice Hall. p. 169.ISBN9780131687431.
^Becchini, R.; Chilaev, P.; Krivtsov, V.; et al. (2003)."Chapter 4: Middleware". In Drira, K.; Martelli, A.; Villemur, T. (eds.).Cooperative Environments for Distributed Systems Engineering: The Distributed Systems Environment Report. Springer. pp. 41–4.ISBN9783540455820.
^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 fromiEEE Distributed Systems OnlineArchived 2011-09-28 at theWayback Machine