Circuit Breakers, Discovery, and API Gateways in Microservices

Montesi, Fabrizio; Weber, Janine

doi:10.48550/arxiv.1609.05830

Cited by 15 publications

(33 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Literature which does not include any of these elements was excluded from this review. This was the case for 35…”

Section: Collecting the Literature Bodymentioning

confidence: 68%

Identification of Practices and Capabilities in API Management: A Systematic Literature Review

Mathijssen,

Overeem,

Jansen

2020

Preprint

View full text Add to dashboard Cite

Traditional organizations are increasingly becoming software producing organizations. This software is enabling them to integrate business processes between different departments and with other organizations through Application Programming Interfaces (APIs). The main task of managing APIs is to ensure that the APIs are easy to use by third parties, such as providing helpful documentation, monitoring API performance, and even monetizing API usage. The knowledge on API management is scattered across academic literature. In this document, we describe a Systematic Literature Review (SLR) that has the goal of collecting API Management practices and capabilities related to API Management, as well as proposing a comprehensive definition of the topic. In the scope of this work, a practice is defined as any practice that has the express goal to improve, encourage and manage the usage of APIs. Capabilities are defined as the ability to achieve a certain goal related to API Management, through the execution of two or more interrelated practices.We follow a standard method for SLRs in software engineering. We managed to collect 24 unique definitions for the topic, 114 practices and 39 capabilities.

show abstract

“…Literature which does not include any of these elements was excluded from this review. This was the case for 35…”

Section: Collecting the Literature Bodymentioning

confidence: 68%

Identification of Practices and Capabilities in API Management: A Systematic Literature Review

Mathijssen,

Overeem,

Jansen

2020

Preprint

View full text Add to dashboard Cite

show abstract

“…Example 4.3 (Polymorphic API Gateway). In the software paradigm of microservices [Dragoni et al 2017], an API gateway (Application Programming Interface gateway) is a polymorphic proxy server that offers a single endpoint through which clients can access other servers [Montesi and Weber 2016]. We can model this behaviour as the following process.…”

Section: ! ( ′ ) ′ ( ) ′ ( ) ⊲mentioning

confidence: 99%

Linear Logic, the $π$-calculus, and their Metatheory: A Recipe for Proofs as Processes

Montesi¹,

Peressotti²

2021

Preprint

Self Cite

View full text Add to dashboard Cite

The Curry-Howard correspondence between natural deduction and the -calculus has provided a canonical foundation for the study of typed functional languages. Initiated by Abramsky [1994], the Proofs as Processes agenda is to establish a similar foundation for the study of concurrent languages, by researching the connection between linear logic [Girard 1987] and the -calculus [Milner et al. 1992].To date, Proofs as Processes is still a partial success. Caires and Pfenning [2010] and Wadler [2014] showed that linear propositions correspond to session types: structured communication protocols that prescribe the observable behaviour of processes [Honda 1993]. Further, Carbone et al. [2018b, , and Kokke et al. [2019] demonstrated that adopting devices from hypersequents [Avron 1991] shapes proofs (typing derivations) such that they correspond to the expected syntactic structure of processes in the -calculus. What remains is reconstructing the expected metatheory of session types and the -calculus. In particular, the hallmark of session types is session fidelity: an operational correspondence between the observable behaviours of processes and their session types, formulated via labelled transition systems. To date, this result still has to be reconstructed for Proofs as Processes, because it is unclear how a transition system for session types can arise from linear logic.In this article, we present LL, a new process calculus rooted in linear logic. The key novelty of LL is that it comes with a carefully formulated design recipe for Proofs as Processes, which is based on a dialgebraic view of labelled transition systems and their homomorphisms [Ciancia 2013]. Thanks to our recipe, LL offers the first reconstruction of the expected labelled transition systems of session types based on linear logic, which we use to establish session fidelity for Proofs as Processes. In general, we use LL to carry out the first thorough investigation of the metatheoretical properties enforced by linear logic on the observable behaviour of processes, uncovering connections with standard relations such as similarity and bisimilarity. We also prove that LL and our recipe offer a robust basis for the further exploration of Proofs as Processes, by considering different features and extensions: polymorphism, higher-order communications (code mobility), and recursion. Our higher-order extension of LL, called HO LL, operates as a higher-order linear logic that enforces linear usage of process variables.

show abstract

“…The importance of resilience has been pointed out in many practitioner books of microservices [14][15] [16], and studies discussing key features of MSA Systems [6] [28], which makes it a common sense that resilience is a key characteristic in MSA Systems. In these books and studies, some typical resilience mechanisms like the Circuit Breakers and Bulkheads [8] are mentioned.…”

Section: B Resilience In Microservicesmentioning

confidence: 99%

“…API Gateway, Message Queue, Service Registry, etc.). Threats come from anywhere in an MSA System: small-density components with faults [7], unstable message passing among microservices [8], the underlying cloud environment with unreliable containers, virtual machines, or bare-metal servers [9]. Even normal actions taken in cloud environments like software/hardware upgrades and dynamic changes in configuration files may lead to severe service outages, which are lessons learned from hundreds of service outage reports of cloud companies in the literature [10].…”

Section: Introductionmentioning

confidence: 99%

“…As a result, many practitioners of the Microservice Architecture [14][15] [16], proposed Resilience as a characteristic describing how an MSA System copes with the occurrence of failures and recovers the degraded service back to its normal performance. Existing reliability/fault tolerant mechanisms used in Service-Oriented Architectures and cloud platforms like Circuit Breakers and Bulkheads, are used as resilience mechanisms in MSA Systems [8] [15].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

On Representing Resilience Requirements of Microservice Architecture Systems

Yin

2019

Preprint

View full text Add to dashboard Cite

Together with the spread of DevOps practices and container technologies, Microserivce Architecture has become a mainstream architecture style in recent years. Resilience is a key characteristic in Microservice Architecture Systems(MSA Systems), and it shows the ability to cope with various kinds of system disturbances which cause degradations of services. However, due to lack of consensus definition of resilience in the software field, although many works have been done on resilience for MSA Systems, developers still don't have a clear idea on how resilient an MSA System should be, and what resilience mechanisms are needed.In this paper, by referring to existing systematic studies on resilience in other scientific areas, the definition of microservice resilience is provided and a Microservice Resilience Measurement Model is proposed to measure service resilience. And we give a requirement model to represent resilience requirements of MSA Systems. A process framework is also proposed to elicit MSA System resilience requirements. As a proof of concept, a case study is conducted on an MSA System to illustrate how the resilience requirements are elicited and represented.

show abstract

Circuit Breakers, Discovery, and API Gateways in Microservices

Cited by 15 publications

References 15 publications

Identification of Practices and Capabilities in API Management: A Systematic Literature Review

Identification of Practices and Capabilities in API Management: A Systematic Literature Review

Linear Logic, the $π$-calculus, and their Metatheory: A Recipe for Proofs as Processes

On Representing Resilience Requirements of Microservice Architecture Systems

Contact Info

Product

Resources

About