Microservices: yesterday, today, and tomorrow

Dragoni, Nicola; Giallorenzo, Saverio; Lafuente, Alberto; Mazzara, Manuel; Montesi, Fabrizio; Mustafin, Ruslan; Сафина, Лариса

doi:10.48550/arxiv.1606.04036

Cited by 5 publications

(12 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Infrastructure services implement the same tasks as in MSA. In addition, there is a significant difference in service ownership as development teams are responsible for full support and development of a service throughout its life cycle (also known as the "you build, you run it" principle) [17]. Microservices are small, fine-grained services (hence "micro"), whereas services in SOA range in size from very small to large enterprise services.…”

Section: Related Work 21 Comparison Of Msa With Other Architectural S...mentioning

confidence: 99%

“…Unless the application is becoming too big, monolithic applications are easier to develop [24]. However, large monolithic applications suffer from the following problems [17]: they are difficult to maintain and evolve, it is hard to add or update libraries due to dependency hell, change in only one module requires rebooting the whole application, etc. Microservices succeed in mitigating these problems and are gaining in popularity due to the following characteristics:…”

Section: Related Work 21 Comparison Of Msa With Other Architectural S...mentioning

confidence: 99%

“…Size: Because microservices implement a limited amount of functionalities, their code bases are small which limits the scope of a bug [17]. The small size also provides benefits in terms of service maintainability and extendability.…”

mentioning

confidence: 99%

“…Independence: Each microservice in MSA is operationally independent of others and communicates with other microservices through their published interfaces [25]. This has several benefits: (i) microservices are independently deployed, (ii) the new version of microservice can co-exist with the old version, and the microservices that use the old microservice can be gradually modified to use the new microservice [17], (iii) changes in one microservice do not require the reboot of the whole system, and (iv) scaling MSA implies deploying or disposing of instances of microservices with respect to their load [26].…”

mentioning

confidence: 99%

See 3 more Smart Citations

Developing Microservice-Based Applications Using the Silvera Domain-Specific Language

Suljkanović¹,

Milosavljević

Inđić

et al. 2022

Applied Sciences

View full text Add to dashboard Cite

Microservice Architecture (MSA) is a rising trend in software architecture design. Applications based on MSA are distributed applications whose components are microservices. MSA has already been adopted with great success by numerous companies, and a significant number of published papers discuss its advantages. However, the results of recent studies show that there are several important challenges in the adoption of microservices such as finding the right decomposition approach, heterogeneous technology stacks, lack of relevant skills, out-of-date documentation, etc. In this paper, we present Silvera, a Domain-Specific Language (DSL), and a compiler for accelerating the development of microservices. Silvera is a declarative language that allows users to model the architecture of microservice-based systems. It is designed so that it can be used both by inexperienced and experienced developers. The following characteristics distinguish Silvera from similar tools: (i) lightweight and editor-agnostic language, (ii) built with heterogeneity in mind, (iii) uses microservice-tailored metrics to evaluate the architecture of the designed system, and (iv) automatically generates the documentation. Silvera’s retargetable compiler transforms models into runnable code and produces the documentation for each microservice in the model. The compiler can produce code for any programming language or framework since code generators are registered as plugins. We present a case study that illustrates the use of Silvera and also discuss some current limitations and development directions. To evaluate Silvera, we conducted a survey based on A Framework for Qualitative Assessment of DSLs (FQAD), where we focused on the following DSL characteristics: functional suitability, usability, reliability, productivity, extendability, and expressiveness. Overall, the survey results show that Silvera satisfies these characteristics.

show abstract

Section: Related Work 21 Comparison Of Msa With Other Architectural S...mentioning

confidence: 99%

Section: Related Work 21 Comparison Of Msa With Other Architectural S...mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

Developing Microservice-Based Applications Using the Silvera Domain-Specific Language

Suljkanović¹,

Milosavljević

Inđić

et al. 2022

Applied Sciences

View full text Add to dashboard Cite

show abstract

“…Several systematic literature reviews and surveys focus on de ning the fundamental properties of microservices and the challenges of adopting them. ey range in their rigour: some follow a rigorous search protocol [45,46,90,106,119,228,253,271] while others are less formal [68].…”

Section: Related Studiesmentioning

confidence: 99%

Microservice Transition and its Granularity Problem: A Systematic Mapping Study

Hassan¹,

Bahsoon²,

Kazman³

2019

Preprint

View full text Add to dashboard Cite

Microservices have gained wide recognition and acceptance in so ware industries as an emerging architectural style for autonomic, scalable, and more reliable computing. e transition to microservices has been highly motivated by the need for be er alignment of technical design decisions with improving value potentials of architectures. Despite microservices' popularity, research still lacks disciplined understanding of transition and consensus on the principles and activities underlying "micro-ing" architectures. In this paper, we report on a systematic mapping study that consolidates various views, approaches and activities that commonly assist in the transition to microservices. e study aims to provide a be er understanding of the transition; it also contributes a working de nition of the transition and technical activities underlying it. We term the transition and technical activities leading to microservice architectures as microservitization. We then shed light on a fundamental problem of microservitization: microservice granularity and reasoning about its adaptation as rst-class entities. is study reviews state-of-the-art and -practice related to reasoning about microservice granularity; it reviews modelling approaches, aspects considered, guidelines and processes used to reason about microservice granularity. is study identi es opportunities for future research and development related to reasoning about microservice granularity.CCS Concepts: •General and reference → Surveys and overviews; •So ware and its engineering → Extra-functional properties; Designing so ware; So ware design tradeo s; Abstraction, modeling and modularity; So ware design engineering; Agile so ware development; Publish-subscribe / event-based architectures; Model-driven so ware engineering; Ultra-large-scale systems; Rapid application development; Design pa erns;

show abstract

Message from the AMS Chairs

Lago

Bosman²

2017

2017 IEEE International Conference on Software Architecture Workshops (ICSAW)

View full text Add to dashboard Cite

General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.

show abstract

Microservices: yesterday, today, and tomorrow

Cited by 5 publications

References 0 publications

Developing Microservice-Based Applications Using the Silvera Domain-Specific Language

Developing Microservice-Based Applications Using the Silvera Domain-Specific Language

Microservice Transition and its Granularity Problem: A Systematic Mapping Study

Message from the AMS Chairs

Contact Info

Product

Resources

About