Microservices: Design, Programming, and Operations

A special issue of Electronics (ISSN 2079-9292). This special issue belongs to the section "Computer Science & Engineering".

Deadline for manuscript submissions: 30 September 2024 | Viewed by 699

Special Issue Editors


E-Mail Website
Guest Editor
Department of Computer Science, University of Pisa, Pisa 56127, Italy
Interests: cloud-edge continuum; software engineering; microservices; cybersecurity; green computing; automated reasoning

E-Mail Website
Guest Editor
University of Oulu, Pentti Kaiteran katu 1, Oulu, 90570, Finland
Interests: empirical software engineering; software quality; maintenance and evolution

E-Mail Website
Guest Editor
Computer Science, Baylor University, One Bear Place #97141, Waco, TX 76798, USA
Interests: code-analysis; distributed systems
Special Issues, Collections and Topics in MDPI journals

E-Mail Website
Guest Editor
Department of Computer Science, University of Pisa, Pisa 56127, Italy
Interests: microservices; cloud-native; service-oriented architectures; deployment automation; distributed systems
Special Issues, Collections and Topics in MDPI journals

E-Mail Website
Guest Editor
Department of Computer Science, University of Pisa, Pisa 56127, Italy
Interests: service; cloud and fog computing; coordination and adaptation of software elements; application of formal methods

Special Issue Information

Dear Colleagues,

Microservices are being increasingly adopted in enterprise IT, as many large companies have embraced these architectures to deliver software services to their users. Microservices constitute an alternative to traditional software architectures and offer several advantages, such as enhanced adaptability, scalability, and resilience to failures. Furthermore, microservices facilitate expedited and more streamlined development processes, while promoting cross-collaboration among DevOps teams. As the technological landscape evolves and grows more intricate, the significance of microservices in constructing scalable and efficient applications is evident.

This Special Issue will collect extended contributions from the 5th International Conference on Microservices (MICROSERVICES 2023), Pisa, October 10-12, 2023, and is open to spontaneous original contributions from researchers and practitioners worldwide.

Topics of interests include, but are not limited to, the following:

  • Software engineering methods for microservices, specifically (but not limited to) agile service design practices, behavior- and domain-driven design;
  • Formal models for microservices;
  • Programming languages, notations, and techniques for microservices;
  • Verification (both static and runtime) of microservice systems;
  • Testing for microservices: unit tests, system tests, acceptance and regression tests, test-driven service development;
  • DevOps for microservices, in particular (but not limited to) continuous deployment and distributed monitoring;
  • Microservices in the context of development, security, and operations (DevSecOps);
  • Secure by design in the context of microservices;
  • Microservice operation and contributor analysis;
  • Microservice management: fault, configuration, accounting/cost, performance, security;
  • Co-change and change impact analysis;
  • Discovery/recovery and reverse engineering of microservices solutions;
  • Microservice evolution;
  • Global governance for microservices;
  • Methodologies for identification, specification, and realization of candidate services;
  • Patterns for cloud-native application architectures; service API design and management;
  • Microservices infrastructure components: API gateways, side cars, and service meshes; reactive messaging brokers; service registries; service containers and cluster managers; infrastructure as code;
  • Function-as-a-service and serverless cloud offerings; service-based event sourcing and data streaming architectures;
  • Microservice architectures for the cloud-edge computing continuum;
  • Security and other service quality concerns (consistency, availability, recoverability) in microservices; dealing with General Data Protection Regulation (GDPR) compliance and other data privacy requirements;
  • testing for microservices: unit tests, system tests, acceptance and regression tests, test-driven service development;
  • Internet technologies: services, human interactions, data analytics and AI for IoT, architecture things centric, sensor networks, security, privacy, applications;
  • AI and microservices (including datasets, open-source technology);
  • Cyber-physical systems: AI/ML applications, security;
  • Industrial case studies and applications: data science/big data, smart industry, healthcare, government, manufacturing, logistics and supply chain management;
  • Empirical studies of microservices adoption;
  • Case studies and surveys on the topic of microservices;
  • Sustainable practices in the microservices community;
  • Education about microservices technologies.

Dr. Stefano Forti
Dr. Valentina Lenarduzzi
Dr. Tomas Cerny
Dr. Jacopo Soldani
Prof. Dr. Antonio Brogi
Guest Editors

Manuscript Submission Information

Manuscripts should be submitted online at www.mdpi.com by registering and logging in to this website. Once you are registered, click here to go to the submission form. Manuscripts can be submitted until the deadline. All submissions that pass pre-check are peer-reviewed. Accepted papers will be published continuously in the journal (as soon as accepted) and will be listed together on the special issue website. Research articles, review articles as well as short communications are invited. For planned papers, a title and short abstract (about 100 words) can be sent to the Editorial Office for announcement on this website.

Submitted manuscripts should not have been published previously, nor be under consideration for publication elsewhere (except conference proceedings papers). All manuscripts are thoroughly refereed through a single-blind peer-review process. A guide for authors and other relevant information for submission of manuscripts is available on the Instructions for Authors page. Electronics is an international peer-reviewed open access semimonthly journal published by MDPI.

Please visit the Instructions for Authors page before submitting a manuscript. The Article Processing Charge (APC) for publication in this open access journal is 2400 CHF (Swiss Francs). Submitted papers should be well formatted and use good English. Authors may use MDPI's English editing service prior to publication or during author revisions.

Keywords

  • microservice-based architectures
  • software and its engineering
  • application management
  • DevOps
  • microservices security
  • AI

Published Papers (1 paper)

Order results
Result details
Select all
Export citation of selected articles as:

Review

16 pages, 364 KiB  
Review
From Microservice to Monolith: A Multivocal Literature Review
by Ruoyu Su, Xiaozhou Li and Davide Taibi
Electronics 2024, 13(8), 1452; https://doi.org/10.3390/electronics13081452 - 11 Apr 2024
Viewed by 404
Abstract
Recently, the phenomenon of switching back from microservice to monolith has increased in frequency, leading to intense debate in the industry. In this paper, we conduct a multivocal literature review to investigate reasoning and key aspects to pay attention to when switching back [...] Read more.
Recently, the phenomenon of switching back from microservice to monolith has increased in frequency, leading to intense debate in the industry. In this paper, we conduct a multivocal literature review to investigate reasoning and key aspects to pay attention to when switching back and analyze other practitioners’ opinions. The results show four cases of switching back from microservice to monolith: Istio control plane, Amazon Prime Video monitoring service, Segment, and InVision. The five main reasons that led to switching back are cost, complexity, scalability, performance, and organization. During the switching back process, six key aspects need to be addressed: (1) stopping the development of more services, (2) consolidating and testing paths, (3) unifying data storage, (4) implementing the message bus principle, (5) giving up diverse techniques, and (6) learning to use modular design principles. As to the practitioners’ opinions, they had mixed views about the switching back phenomenon. However, most thought that switching back required consideration of the actual system situation and principles. These results pave the way for further research and guide researchers and companies through the process of switching back from microservice to monolith. Full article
(This article belongs to the Special Issue Microservices: Design, Programming, and Operations)
Show Figures

Figure 1

Back to TopTop