2018
DOI: 10.1007/978-3-319-74781-1_12
|View full text |Cite
|
Sign up to set email alerts
|

Design-Time to Run-Time Verification of Microservices Based Applications

Abstract: Microservice based architectures have started to gain in popularity and are often adopted in the implementation of modern cloud, IoT, and large-scale distributed applications. Software life cycles, in this context, are characterized by short iterations, where several updates and new functionalities are continuously integrated many times a day. This paradigm shift calls for new formal approaches to systematic verification and testing of applications in production infrastructures. We introduce an approach to con… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(8 citation statements)
references
References 15 publications
0
8
0
Order By: Relevance
“…Software architects who aim to optimize the system as a whole need to understand each module's internal characteristics and thus be able to locate important module aspects in the code, but given the possible mix of languages or frameworks, it becomes hard to assess the overall system by hand and perform global optimization and consistency verification. Even routine testing becomes a burden [43], [44].…”
Section: General Challenges With Microservicesmentioning
confidence: 99%
See 2 more Smart Citations
“…Software architects who aim to optimize the system as a whole need to understand each module's internal characteristics and thus be able to locate important module aspects in the code, but given the possible mix of languages or frameworks, it becomes hard to assess the overall system by hand and perform global optimization and consistency verification. Even routine testing becomes a burden [43], [44].…”
Section: General Challenges With Microservicesmentioning
confidence: 99%
“…Besides, this process of concern centralization can provide access to the up-to-date system documentation, which is currently difficult to access since modules change often, and the documentation easily gets out-dated. Similarly, there is a notable delay in co-evolution between the system source code and tests [158], which further facilitates the introduction of errors, not to mention that current integration test approaches resort to only consider the high-level module interaction [43], [44] due to the complexity and difficulties related to accessing system details. We highlight the centralization for concerns scattered across distributed system modules in Figure 1.…”
Section: The Aspect-oriented Perspectivementioning
confidence: 99%
See 1 more Smart Citation
“…In the studies relevant to interoperability and integration testing of IoT systems, a variety of testing techniques and approaches have been researched and applied, from formal verifications [13] to informal crowdsourcing techniques that can be compared to exploratory testing [22].…”
Section: Rq5: Used Testing Techniques and Approachesmentioning
confidence: 99%
“…Furthermore, aspects such as messaging, communication protocols, which are commonly used in concurrent or distributed systems, can be difficult to model with the language primitives of timed-automata [22,21]. Moreover, TB nets are supported by powerful off-the-shelf open source software tools able to perform simulation, model checking [23,24,25,26], model-based testing, and runtime verification [27,28].…”
Section: Time Basic Petri Netsmentioning
confidence: 99%