From the decorator pattern to circuit breakers in microservices

Montesi, Fabrizio; Weber, Janine

doi:10.1145/3167132.3167427

Cited by 15 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are some other resources concerning about API gateway's primary functionalities. Montesi et al 48 and Chandramouli et al 49 both point out the primary function of the API gateway is publishing multiple APIs to services of different natures. Since the API gateway serves as the entry point for microservices, this concern is often related to Microservices security , such as access control, security logging, circuit breakers, and so on.…”

Section: Resultsmentioning

confidence: 99%

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

2021

View full text Add to dashboard Cite

The microservice application programming interface (API) becomes a growing concern in the IT industry, as a result of the increasing usage of microservice architecture style. There exist many successful practices among companies, communities, and so on. In contrast, the related academic research is still at an early stage, where lacks an overview of technologies for the design, implementation and operation of microservice APIs, as well as a general picture of concerns. In this article, we try to fill this gap by eliciting the technologies and concerns on microservice APIs and establishing a microservice API description model, with the intention of aiding researchers to gain an overview of this field and find possible research directions, and helping practitioners to better understand microservice APIs and be aware of the existing approaches for daily work. Twelve academic papers and 38 gray literatures are selected and analyzed following the systematic literature review approach. Besides, we give our observations from this study. For researchers, our findings show the most cared concerns of practitioners, and our description model can be used as a reference for new theories, experiments, and future research dimensions. For practitioners, our study can be used as a guideline for microservices experimentation and a starting point for practice.

show abstract

Section: Resultsmentioning

confidence: 99%

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

2021

View full text Add to dashboard Cite

show abstract

“…M. Hafiz published a pattern called Unique Atomic Chunks that assures a cleaner locking for access to shared files; however, it is not clear why it is also a reliability or security pattern, as he implies in [82]. Montesi and Weber [83] described the Circuit Breaker as a pattern for preventing cascading failures by guarding service calls; this pattern is implemented as a Decorator [10] applied to the interface of the service. Asnar et al developed organizational patterns for security and dependability [84]; these patterns consider the interaction of humans and systems and, as such, are particularly interesting and different from most of the patterns discussed here.…”

Section: Specialized Patterns and Related Artifacts 61 Hybrid Patternsmentioning

confidence: 99%

“…A Circuit Breaker handles faults that might take a variable amount of time (such as transient faults, slow network connections, timeouts, etc.) to recover from when connecting to a remote service or resource [83,93,133].…”

Section: Dependability Patternsmentioning

confidence: 99%

Dependability Patterns: A Survey

Buckley,

Fernandez

2023

Computers

View full text Add to dashboard Cite

Patterns embody the experience and knowledge of designers and are effective ways to improve nonfunctional aspects of software systems. Although there are several catalogs and surveys of security patterns, there is no catalog or general survey about dependability patterns. Our survey presented an enumeration of dependability patterns, which include fault tolerance, reliability, safety, and availability patterns. After defining classification groups and showing basic pattern relationships, we showed the references to the publications where these patterns were introduced and enumerated their intents. Another objective was evaluating these patterns to see if their descriptions are appropriate for a possible catalog, which would make them useful to developers and researchers. We found that most of them need remodeling because they use ad hoc templates or no templates. We considered some models from which we can derive patterns and methodologies that incorporate the use of patterns to build dependable software systems. We also provided directions for research.

show abstract

“…By doing so, microservices communication problems can be mitigated as the circuit breaker prevents errors propagation by returning to the caller without performing any action. As a matter of fact, several works 39,40 suggest the adoption of circuit breakers in developing microservices‐based applications and solutions have already been implemented in practice. For example, Kubernetes implements a rather simple circuit‐breaking mechanism by unhooking failed Pods from their matching services 21…”

Section: Related Workmentioning

confidence: 99%

A framework for microservices synchronization

Iasio

Zimeo

2020

Softw Pract Exp

View full text Add to dashboard Cite

Microservices architecture and continuous software engineering are becoming popular approaches for developing and operating software products. The enabling feature of this success is the independence of the execution environments hosting microservices: by insulating failures and versioning in specific microservices, a complex application benefits of high availability at runtime and agility at development time. However, execution independence does not mean functional independence. Microservices need to interact among them to fulfill a common goal of an application. The unavailability of a microservice may seriously impact other dependent microservices, limiting continuity. To address this new kind of problem in microservices architecture, we argue the necessity of a synchronization mechanism able to support microservices coordination according to their running states: dependent microservices should wait for unready ones to avoid useless and faulty interactions. In this article, we propose a new framework, Synchronizer, able to support synchronization among microservices by exploiting distributed registries for collecting health/state information about deployed containers and hosted microservices. It has been implemented for the OpenShift platform and validated in different use cases: for example, for coordinating applications bootstrap and for programming scripts of continuous deployment orchestrators, such as Jenkins. In both cases, Synchronizer worked as expected and showed the positive effects of synchronization, giving us a valuable feedback about the possibility of further extending its application and of integrating the feature in existing microservices frameworks (eg, services mesh).

show abstract

From the decorator pattern to circuit breakers in microservices

Cited by 15 publications

References 8 publications

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

Dependability Patterns: A Survey

A framework for microservices synchronization

Contact Info

Product

Resources

About