Designing programs that check their work
STOC '89 Proceedings of the twenty-first annual ACM symposium on Theory of computing
Writing correct software with Eiffel
Dr. Dobb's Journal
EPL—parallel programming with recurrent equations
Parallel functional languages and compilers
Para-functional programming in Haskell
Parallel functional languages and compilers
Crystal: theory and pragmatics of generating efficient parallel code
Parallel functional languages and compilers
Software reliability via run-time result-checking
Journal of the ACM (JACM)
CoG kits: a bridge between commodity distributed computing and high-performance grids
Proceedings of the ACM 2000 conference on Java Grande
Communications of the ACM
Data management and transfer in high-performance computational grid environments
Parallel Computing - Parallel data-intensive algorithms and applications
A Resource Management Architecture for Metacomputing Systems
IPPS/SPDP '98 Proceedings of the Workshop on Job Scheduling Strategies for Parallel Processing
Specification of grid workflow applications with AGWL: an Abstract Grid Workflow Language
CCGRID '05 Proceedings of the Fifth IEEE International Symposium on Cluster Computing and the Grid (CCGrid'05) - Volume 2 - Volume 02
ASKALON: A Grid Application Development and Computing Environment
GRID '05 Proceedings of the 6th IEEE/ACM International Workshop on Grid Computing
Future Generation Computer Systems
| Hi-index | 0.00 |
The so called ''invisible Grid'', transparent to application developers, is still far from being a reality. One reason is that the workflow model, which emerged as a widely accepted paradigm for high-level composition of Grid applications, is based on a low-level imperative programming model prone to programming errors. The issue of developing correct (bug-free) Grid applications has not been addressed by the community. We propose a new model for building Grid applications based on two programming phases: (1) formal functional specification, written by the application developer not interested in any Grid-related issues; (2) imperative workflow-based coordination, written by the computer scientist, which ports and efficiently executes the specification onto the Grid. A correctness checker automatically connects both parts at compile-time and insures the correct execution of the workflow coordination with respect to the formal specification. We validate our approach for three scientific applications and show real-world experimental results that demonstrate the scalability of our coordination model and the fact that the overhead introduced by our correctness checker is insignificant when compared to the latencies exhibited by the Grid middleware software.