Aspect-Oriented Programing Techniques to support Distribution, Fault Tolerance, and Load Balancing in the CORBA-LC Component Model

Abstract

The design and implementation of distributed High Performance Computing (HPC) applications is becoming harder as the scale and number of distributed resources and application is growing. Programming abstractions, libraries and frameworks are needed to better overcome that complexity. Moreover, when Quality of Service (QoS) requirements such as load balancing, efficient resource usage and fault tolerance have to be met, the resulting code is harder to develop, maintain, and reuse, as the code for providing the QoS requirements gets normally mixed with the functionality code. Component Technology, on the other hand, allows a better modularity and reusability of applications and even a better support for the development of distributed applications, as those applications can be partitioned in terms of components installed and running (deployed) in the different hosts participating in the system. Components also have requirements in forms of the aforementioned non-functional aspects. In our approach, the code for ensuring these aspects can be automatically generated based on the requirements stated by components and applications, thus leveraging the component implementer of having to deal with these non-functional aspects. In this paper we present the characteristics and the convenience of the generated code for dealing with load balancing, distribution, and fault-tolerance aspects in the context of CORBA-LC. CORBA-LC is a lightweight distributed reflective component model based on CORBA that imposes a peer network model in which the whole network acts as a repository for managing and assigning the whole set of resources: components, CPU cycles, memory, etc.

A Game Comparative Study: Object-Oriented Paradigm and Notification-Oriented Paradigm

“…In this sense, well-designed software composed of modules as decoupled as possible, using advanced and quite complicated software engineering concepts such as aspects [13] and axiomatic design [37], can help distribution. Still, middleware such as CORBA and RMI would be helpful in terms of infrastructure to some types of module distribution, if there is enough module decoupling [1,13,38,39].…”

“…Still, middleware such as CORBA and RMI would be helpful in terms of infrastructure to some types of module distribution, if there is enough module decoupling [1,13,38,39].…”

“…In spite of those advances, distribution of single code elements or even code modules is still a complex activity demanding research efforts [13,14,17,35,40]. It would be necessary additional efforts to achieve easiness in distribution (e.g.…”

Fault-Tolerance for Component-Based Systems - An Automated Middleware Specialization Approach

“…al., [16] describe an automatic code generation approach for distribution, fault tolerance and load balancing aspects of component based systems. GRAFT on the other hand provides mechanisms that specifically support group failure recovery semantics based on the model-as well as code-based weaving of component-based systems along with runtime monitoring infrastructure support.…”

Aspect Oriented Decision Making Model for Byzantine Agreement

“…They have analyzed and summarized several exception fault types of AspectJ and illustrated the way with appropriate examples to analyze the impact of exception faults on program control flow. Sevilla et al (2007) envisaged the role of Aspect Oriented Programming in distributed component services with respect to distribution, fault tolerance and load balancing. Usually the code for providing QoS parameters (both functional and non-functional) is merged with the business logic and hence it is harder to develop, maintain and reuse the code.…”