1998
DOI: 10.1002/(sici)1097-024x(199807)28:7<703::aid-spe173>3.0.co;2-j
|View full text |Cite
|
Sign up to set email alerts
|

Reusable coordinator modules for massively concurrent applications

Abstract: SUMMARYIsolating computation and communication concerns into separate pure computation and pure coordination modules enhances modularity, understandability and reusability of parallel and/or distributed software. MANIFOLD is a pure coordination language that encourages this separation. We use real, concrete, running MANIFOLD programs to demonstrate the concept of pure coordination modules and the advantage of their reuse in applications of different natures. Performance results for the examples presented in th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Year Published

1998
1998
2018
2018

Publication Types

Select...
4
2
1

Relationship

3
4

Authors

Journals

citations
Cited by 19 publications
(12 citation statements)
references
References 13 publications
0
12
0
Order By: Relevance
“…The same MANIFOLD modules developed for one application may be used in other parallel applications with the same or similar cooperation protocol, regardless of the fact that the two applications may perform completely different computations (the sparse-grid and semi-sparse-grid application use the same protocol manifold; see also [12] for this notion of reusability). Another important advantage of MANIFOLD is that it makes no distinction (from the language point of view) between distributed and parallel environments; the same MANIFOLD code can run in both, as we show in our 'toy' application in Section 2.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…The same MANIFOLD modules developed for one application may be used in other parallel applications with the same or similar cooperation protocol, regardless of the fact that the two applications may perform completely different computations (the sparse-grid and semi-sparse-grid application use the same protocol manifold; see also [12] for this notion of reusability). Another important advantage of MANIFOLD is that it makes no distinction (from the language point of view) between distributed and parallel environments; the same MANIFOLD code can run in both, as we show in our 'toy' application in Section 2.…”
Section: Discussionmentioning
confidence: 99%
“…One important advantage is that it results in a clear separation between the modules responsible for computation (the workers) and the modules responsible for co-ordination (the managers). This strengthens the modularity and enhances the reusability of both types of modules (see [1,9,12]). …”
Section: The Manifold Co-ordination Languagementioning
confidence: 90%
“…The notion of component in σπ is similar to that of Manifold's, and makes it possible for to acquire and replace the implementation of a component at run-time, possibly from some independent vendor over the net [6]. This notion supports the same kind of pluggability as obtained in the Java language [16] by separating interfaces from classes.…”
Section: Conclusion and Related Workmentioning
confidence: 99%
“…Therefore, it is irrelevant what it coordinates. Our M UQE manifold can just as happily orchestrate the cooperation of any pair of processes that have the same input/output and event behavior as UQE and WORKER do, regardless of what computation they perform (see also [ABBE96] for this phenomena).…”
Section: Restructuring the Uqe Transformationmentioning
confidence: 99%