Microservices in Practice, Part 1: Reality Check and Service Design

Pautasso, Cesare; Zimmermann, Olaf; Amundsen, Mike; Lewis, James W.; Josuttis, Nicolai M.

doi:10.1109/ms.2017.24

Cited by 99 publications

(62 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The decomposition of a system into small services, monitoring, and managing these services are among the other important factors that need to be considered. Therefore, migrating to the cloud, and in particular, migrating through cloud‐native architectures, like microservices, is a multidimensional problem . In the absence of a well‐thought methodology, migration can be a trial‐and‐error endeavor, which not only can waste a lot of time but also may lead to a suboptimal solution .…”

Section: Introductionmentioning

confidence: 99%

“…Therefore, migrating to the cloud, and in particular, migrating through cloud-native architectures, like microservices, is a multidimensional problem. [4][5][6] In the absence of a well-thought methodology, migration can be a trial-and-error endeavor, which not only can waste a lot of time but also may lead to a suboptimal solution. 5 Furthermore, given the wide variety of factors (including differing requirements and the skills of team members) in different companies and scenarios, a unique and rigid methodology would not be adequate.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Microservices migration patterns

et al. 2018

View full text Add to dashboard Cite

Summary Microservices architectures are becoming the defacto standard for building continuously deployed systems. At the same time, there is a substantial growth in the demand for migrating on‐premise legacy applications to the cloud. In this context, organizations tend to migrate their traditional architectures into cloud‐native architectures using microservices. This article reports a set of migration and rearchitecting design patterns that we have empirically identified and collected from industrial‐scale software migration projects. These migration patterns can help information technology organizations plan their migration projects toward microservices more efficiently and effectively. In addition, the proposed patterns facilitate the definition of migration plans by pattern composition. Qualitative empirical research is used to evaluate the validity of the proposed patterns. Our findings suggest that the proposed patterns are evident in other architectural refactoring and migration projects and strong candidates for effective patterns in system migrations.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Microservices migration patterns

et al. 2018

View full text Add to dashboard Cite

show abstract

“…More in details, the EdgeX Foundry software architecture is located in the middle layer (i.e., fog layer), being composed of many sub-layers, as described in the following. Such architecture has been conceived starting from the microservice paradigm [13] that enables modular, scalable, secure, and technology-agnostic applications. Specifically, the chosen approach is the loosely-coupled micro-services architecture that requires a common layer to enable communications and data exchanges among modules using Inter-Processes Communications (IPC) APIs (i.e., REST APIs).…”

Section: A Framework For Fog/edge Computingmentioning

confidence: 99%

Fog Computing Architectures: A Reference for Practitioners

Antonini

Vecchio

Antonelli

2019

IEEE Internet Things M.

View full text Add to dashboard Cite

Soon after realizing that Cloud Computing could indeed help several industries overcome classical product-centric approaches in favor of more affordable service-oriented business models, we are witnessing the rise of a new disruptive computing paradigm, namely Fog Computing. Essentially, Fog Computing can be considered as an evolution of Cloud Computing, in the sense that the former extends the latter to the edge of the network (that is, where the connected devices -the thingsare) without discontinuity, realizing the so-called "cloud-tothing continuum". Since its infancy, Fog Computing has been considered as a necessity within several Internet of Things (IoT) domains (one for all: Industrial IoT) and, more generally, wherever embedded artificial intelligence and/or more advanced distributed capabilities were required. Fog Computing cannot be considered only a fancy buzzword: according to separate, authoritative analyses its global market will reach $18 billion by 2022, while nearly 45% of the world's data will be moved to the network edge by 2025. In this paper, we take stock of the situation, summarizing the most modern and mature Fog Computing initiatives from standardization, commercial, and open-source communities perspectives.

show abstract

“…Inter-process communication can be use for similar purposes, but allows applications to communicate with each other. Microservices, for example, use a network connection and communicate through Remote Procedure Calls (RPCs) [50].…”

Section: Cross-language Integration Techniquesmentioning

confidence: 99%

Live Multi-language Development and Runtime Environments

et al. 2018

View full text Add to dashboard Cite

Context: Software development tools should work and behave consistently across different programming languages, so that developers do not have to familiarize themselves with new tooling for new languages. Also, being able to combine multiple programming languages in a program increases reusability, as developers do not have to recreate software frameworks and libraries in the language they develop in and can reuse existing software instead. Inquiry: However, developers often have a broad choice of tools, some of which are designed for only one specific programming language. Various Integrated Development Environments have support for multiple languages, but are usually unable to provide a consistent programming experience due to different languagespecific runtime features. With regard to language integrations, common mechanisms usually use abstraction layers, such as the operating system or a network connection, which are often boundaries for tools and hence negatively affect the programming experience. Approach: In this paper, we present a novel approach for tool reuse that aims to improve the experience with regard to working with multiple high-level dynamic, object-oriented programming languages. As part of this, we build a multi-language virtual execution environment and reuse Smalltalk's live programming tools for other languages. Knowledge: An important part of our approach is to retrofit and align runtime capabilities for different languages as it is a requirement for providing consistent tools. Furthermore, it provides convenient means to reuse and even mix software libraries and frameworks written in different languages without breaking tool support. Grounding: The prototype system Squimera is an implementation of our approach and demonstrates that it is possible to reuse both development tools from a live programming system to improve the development experience as well as software artifacts from different languages to increase productivity. Importance: In the domain of polyglot programming systems, most research has focused on the integration of different languages and corresponding performance optimizations. Our work, on the other hand, focuses on tooling and the overall programming experience. ACM CCS 2012Software and its engineering → Integrated and visual development environments; Runtime environments; Software testing and debugging;

show abstract

Microservices in Practice, Part 1: Reality Check and Service Design

Cited by 99 publications

References 1 publication

Microservices migration patterns

Microservices migration patterns

Fog Computing Architectures: A Reference for Practitioners

Live Multi-language Development and Runtime Environments

Contact Info

Product

Resources

About