2021
DOI: 10.3384/ecp21181393
|View full text |Cite
|
Sign up to set email alerts
|

A Cloud-native Implementation of the Simulation as a Service-Concept Based on FMI

Abstract: Providing modelling and simulation capabilities as a service promises to increase their value by improving accessibility for non-expert users and software agents as well as by leveraging cloud-computing technology to scale simulation performance beyond the capabilities of a single computer. In order to reach this potential, implementations must align their design with the architectural styles of cloud computing applications and the web in general.We present an open-source, cloud-native Simulation as a Service … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2024
2024
2024
2024

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(4 citation statements)
references
References 8 publications
0
4
0
Order By: Relevance
“…From a non-functional perspective, the service should be designed as a Cloud-native Application (CNA) [20] and, consequently, as a Cloud-native Simulation (CNS) system [21, p. 15] because not designing it as a CNA would mean to disregard the expected and proven characteristics for Software as a Service (SaaS) and the corresponding best practices. Consequently, the software should be realized as a microservice, isolate the state in a single component, use containers as deployment units and follow best practices for the development of SaaS (for details see [35]).…”
Section: Methodsmentioning
confidence: 99%
See 3 more Smart Citations
“…From a non-functional perspective, the service should be designed as a Cloud-native Application (CNA) [20] and, consequently, as a Cloud-native Simulation (CNS) system [21, p. 15] because not designing it as a CNA would mean to disregard the expected and proven characteristics for Software as a Service (SaaS) and the corresponding best practices. Consequently, the software should be realized as a microservice, isolate the state in a single component, use containers as deployment units and follow best practices for the development of SaaS (for details see [35]).…”
Section: Methodsmentioning
confidence: 99%
“…For the second hypothesis, machine-actionability will be demonstrated through the API's use by the PPAimplementation as a software that was not specifically programmed to use it. FAIRness and support for loose coupling will be evaluated by comparing the developed hypermedia API to its non-RESTful predecessor (detailed in [35]) for each of the 15 FAIR principles and for each of the coupling facets identified by Pautasso and Wilde [49], respectively.…”
Section: Research Questions and -Hypothesesmentioning
confidence: 99%
See 2 more Smart Citations