Grid-Enabling Applications with JGRIM

Abstract

The development of massively distributed applications with enormous demands for computing power, memory, storage and bandwidth is now possible with the Grid. Despite these advances, building Grid applications is still very difficult. We present JGRIM, an approach to easily gridify Java applications by separating functional and Grid concerns in the application code, and report evaluations of its benefits with respect to related approaches. The results indicate that JGRIM simplifies the process of porting applications to the Grid, and the Grid code obtained from this process performs in a very competitive way compared to the code resulting from using similar tools.

JASAG: a gridification tool for agricultural simulation applications

“…The component‐oriented anatomy is based on reusable software pieces that are compounded in a loosely coupled fashion to form a larger system. This anatomy is found in JGRIM , where specific components from the original sequential application are transformed into Mobile Grid Services (MGS) whose functionalities are exposed via Web services. After transformation, each MGS is able to interact with other MGSs and indirectly use middleware‐level Grid services such as resource management, mobility, and thread execution.…”

“…On the other hand, the second group is composed of more recent tools that materialize semi automatic transformation methods to obtain the Grid counterparts of sequential applications . Examples are Java Generalized Reactive Intelligent Mobility (JGRIM) and EasyFJP . This kind of tools allows users to Grid‐enable applications with low developer intervention, and in many cases, without merging the business logic code with Grid‐specific code.…”

An approach for non-intrusively adding malleable fork/join parallelism into ordinary JavaBean compliant applications

“…In fact, component-based notions are being extensively applied in distributed programming, as evidenced by proposed Grid component models such as the GCM [23,3] and the K-Components [30]. Also, in Java, component-based programming is commonplace [64], given by the high popularity of component models for Java such as JavaBeans [77] and Dependency Injection [49]. For these reasons, we believe the applicability of EasyFJP is not compromised.…”

“…In a broad sense, policies represent a mechanism that allows developers to express, separately from the application logic, customized strategies for applications to achieve better performance [62]. Policies have been widely employed in diverse areas such as mobile distributed computing [66], migratory Web agents [62], and Grid development [64]. Conceptually, a policy implements a user-specified rule that governs the behavior of an application within the underlying execution environment.…”

“…Active object creation, parallelism and mobility must be specified in the application code through API calls. JGRIM [64] is a method for Gridenabling ordinary component-based applications. JGRIM focuses on non-invasively injecting existing Grid middleware services such as component brokering, mobility, and parallelism into sequential codes via Dependency Injection techniques [49].…”