2020
DOI: 10.1007/978-3-030-50029-0_13
|View full text |Cite
|
Sign up to set email alerts
|

Time-Fluid Field-Based Coordination

Abstract: Emerging application scenarios, such as cyber-physical systems (CPSs), the Internet of Things (IoT), and edge computing, call for coordination approaches addressing openness, self-adaptation, heterogeneity, and deployment agnosticism. Field-based coordination is one such approach, promoting the idea of programming system coordination declaratively from a global perspective, in terms of functional manipulation and evolution in "space and time" of distributed data structures, called fields. More specifically, re… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
1
1

Relationship

2
0

Authors

Journals

citations
Cited by 2 publications
(4 citation statements)
references
References 36 publications
(49 reference statements)
0
4
0
Order By: Relevance
“…The contribution of this work extends the earlier version presented at COORDINATION 2020 [20], and can be summarised as follows:…”
Section: Introductionmentioning
confidence: 69%
See 2 more Smart Citations
“…The contribution of this work extends the earlier version presented at COORDINATION 2020 [20], and can be summarised as follows:…”
Section: Introductionmentioning
confidence: 69%
“…Differently from the work in [20], in which a field computation could actually be assigned a single guard policy, here we extend this approach by allowing many guard policies to be associated to an actual field computation, and since guard policies are particular kinds of field computations as well, we also allow guard policies to be stacked at multiple layers, forming a tree structure. So, essentially, platform triggers schedule low-level guard policies, the leafs of the tree, which are field computations enacting low-level (causality-based) "clocks".…”
Section: 1mentioning
confidence: 99%
See 1 more Smart Citation
“…Differently from the work in [PMVZ20], where a field computation could be assigned a single guard policy, here we extend this approach by allowing many guard policies to be associated to an actual field computation, and since guard policies are particular kinds of field computations as well, we also allow guard policies to be stacked at multiple layers, forming a tree structure. So, essentially, platform triggers schedule low-level guard policies, the leafs of the tree, which are field computations enacting low-level (causality-based) "clocks".…”
Section: 1mentioning
confidence: 99%