2017
DOI: 10.1007/978-3-319-59394-4_3
|View full text |Cite
|
Sign up to set email alerts
|

Microservices as Agents in IoT Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0
2

Year Published

2018
2018
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 27 publications
(15 citation statements)
references
References 6 publications
0
13
0
2
Order By: Relevance
“…Ciavotta et al applied the microservices architectural approach to design simulation tools to support the manufacturing lifecycle in factories and for machine‐to‐machine (M2M) interactions. Another solution for M2M service management has been proposed by Krivic et al The authors presented an agent‐based solution based on microservices for establishing M2M bidirectional communication and thereby gain access to the services. While adopting the microservices approach for M2M systems, Namiot and Sneps‐Sneppe suggested that the system may be decomposed into microservices, by splitting across the use cases or by splitting considering the resource being accessed .…”
Section: Domain‐specific Microservice‐based Architecturesmentioning
confidence: 99%
“…Ciavotta et al applied the microservices architectural approach to design simulation tools to support the manufacturing lifecycle in factories and for machine‐to‐machine (M2M) interactions. Another solution for M2M service management has been proposed by Krivic et al The authors presented an agent‐based solution based on microservices for establishing M2M bidirectional communication and thereby gain access to the services. While adopting the microservices approach for M2M systems, Namiot and Sneps‐Sneppe suggested that the system may be decomposed into microservices, by splitting across the use cases or by splitting considering the resource being accessed .…”
Section: Domain‐specific Microservice‐based Architecturesmentioning
confidence: 99%
“…This should also result in a better consistency and synchronisation between the various models representing the design time aspects (notably business) and runtime aspects of the CPPS [7]. • Then, from our models, automate (at least partially) the generation of different software components such as the target MAS in our present case or various software artifacts of the Application Layer in the context of a future DT at La Poste (e.g., micro-services directly implementing various features of the CPPS or micro-services that can be used as agents emulating components of the CPPS [16]). • Provide appropriate views to different stakeholders (e.g., business expert, DT architect, software engineer) over the set of possibly large and heterogeneous models resulting from our MPM approach or from the definition of the future DT at La Poste [8].…”
Section: Next Steps and Related Workmentioning
confidence: 99%
“…The containerized application functionality can be partitioned and easily distributed in the system, as each microservice can be developed with different technologies by different stakeholders and deployed independently. As in [15], microservices can be considered as agents.…”
Section: Mec As a Multi-agent Systemmentioning
confidence: 99%
“…The optimization of task assignment, with negotiating agents, between cloud and edge platforms is addressed in [5]. Lastly, in [15], collaborative microservices are modeled as a MAS for IoT.…”
Section: Introductionmentioning
confidence: 99%