What is a Middleware? A Platform, A Framework or What?
Some time ago I wrote a post about the difference between “platform” and “framework” and recently a reader, Hemanth Gowda, posted a comment to that text, asking how the concept of “middleware” is positioned among those definitions.
In my opinion, the concept of middleware is all about service providing. While a platform allows a software to run and a framework is more focused on software design, a middleware will provide services for your application. These services will allow your application to support many concurrent users, connect to several data sources, interoperate with services provided by other middleware instances, expand the platform to scale the application, support several frameworks to give flexibility for developers and many other relevant features.
The best example of middleware in the Java world is an application server, such as Glassfish, JBoss and Websphere. They provide all features mentioned above and much more. If you develop an application to run in any of these application servers it will a) support multiple users by default; b) be able to connect to several database from different vendors (Oracle, MySQL, MSSQL); c) access web services (stack or rest); d) send emails; e) provide fameworks for logging, data access, user interface rendering; and f) manage multiple instances of the application server to optimize the use of available hardware, among other advantages. The figure below shows the graphical schema of an application server.
There are other kinds of middleware and I would like to emphasize a) message queue systems (MQS) to mainly interchange asynchronous messages between applications; b) enterprise service bus (ESB) to integrate different kind of services provided by several systems; and c) transaction systems to guarantee the consistency of the data involved in the same business operation, such as database management systems.
Comparing middleware with framework and platform, I would say that a middleware system contributes to reduce the complexity of your application, which is one of the main characteristics of a framework, but it is not actually part of your application as a framework is. A middleware will provide many services for your application, but everything (middleware + application) will run on the available platform, which could be a virtual machine, or an operating system or a mobile device, etc.
I appreciate your questions and I love to answer them here! So, do not hesitate to post your comments as Hemanth did. Thanks for the opportunity to discuss the topic.