Middleware is defined in (Mahmoud, 2004) as, “a distributed software layer that sits above the network operating system and below the application layer and abstracts the heterogeneity of the underlying environment”. According to this definition, the purpose of a middleware is to isolate technology. This task requires that a new layer responsible for handling data between two systems be defined,...

Biogrid project is one of national R&D projects on grid in IT-Program granted by Ministry of Education, Culture, Sports, Science and Technology since 2002. In this project, we consider a grid technology as a glue or a middleware to integrate observation devices, databases and computational resources for advanced life science. We have built four typical applications in life science as exemplars ...

General-purpose middleware solutions, by definition, cannot readily support domain-specific semantics without significant manual efforts in specializing the middleware. This paper presents GRAFT (GeneRative Aspects for Fault Tolerance), which is a modeldriven, generative, and aspects-based approach to specialize general-purpose middleware with failure handling and recovery semantics imposed by ...

To realize smart home vision in an equipped domain, several types of context-aware applications should be deployed. Because of complex tasks of context gathering and processing, designing context-aware applications requires middleware support. Designing a context-aware middleware is a challenging issue because of specific characteristics of context and devices such as dynamic nature of context ...

The highly distributed and resource constrained nature of computing in Networked Embedded Systems necessitates an application specific middleware—a kind of distributed operating system that provides global services for the application. We propose to automatically synthesize the middleware from abstract, platform-independent algorithm models. The modeling language captures the temporal and compu...

The number of open specifications of middleware systems and middleware services is increasing. Despite their complexity, they are traditionally described through APIs (the operation signatures) and informal prose (the behaviour). This fact often leads to ambiguities and makes difficult a better understanding of what is really described. In this paper, we adopt software architecture principles f...

Commercially available middleware systems today offer best-effort Quality-of-Service (QoS) to the application programs. Due to the natural limitation of resources and the differences between the priorities and demands of applications, middleware systems must have the capability to offer varying degrees of QoS. The QoS requirements of middleware applications can be monitored and fulfilled by con...

The rapid growth of small Internet connected devices, known as the Internet of Things (IoT), is creating a new set of challenges to create secure, private infrastructures. The purpose of this paper is to review the current literature on the challenges and approaches to security and privacy in the Internet of Things, with an especial focus on how these aspects are handled in IoT middleware. We f...

The development of real-time distributed applications requires middleware providing both reliability and performance. Middleware must be adaptable to meet application requirements and integrate legacy components. Current middleware provides only partial solutions to these issues. Moreover, they newer address all of them. Thus, a new generation of middleware is required. We have introduced the s...

A few years ago, integrating applications simply required putting the right middleware in place. Today, however, the proliferation of different middleware approaches and technologies has complicated matters. Application integration now implies middleware integration. Essentially, we need “middleware for middleware” that allows us to noninvasively integrate disparate middleware systems. The econ...