Analyzing the relevance of SOA patterns for microservice-based systems

Justus Bogner, Alfred Zimmermann, Stefan Wagner

Research output: Chapter in Book / Report / Conference proceedingConference contributionAcademicpeer-review

Abstract

To bring a pattern-based perspective to the SOA vs. Microservices discussion, we qualitatively analyzed a total of 118 SOA patterns from 2 popular catalogs for their (partial) applicability to Microservices. Patterns had to hold up to 5 derived Microservices principles to be applicable. 74 patterns (63%) were categorized as fully applicable, 30 (25%) as partially applicable, and 14 (12%) as not applicable. Most frequently violated Microservices characteristics were Decentralization and Single System. The findings suggest that Microservices and SOA share a large set of architectural principles and solutions in the general space of Service-Based Systems while only having a small set of differences in specific areas.
Original languageEnglish
Title of host publicationZEUS 2018 - Proceedings of the 10th Central European Workshop on Services and their Composition
EditorsN. Herzberg, C. Hochreiner, O. Kopp, J. Lenhard
PublisherCEUR-WS
Pages9-16
Volume2072
Publication statusPublished - 2018
Externally publishedYes
Event10th Central European Workshop on Services and their Composition, ZEUS 2018 - Dresden, Germany
Duration: 8 Feb 20189 Feb 2018

Publication series

NameCEUR Workshop Proceedings
ISSN (Print)1613-0073

Conference

Conference10th Central European Workshop on Services and their Composition, ZEUS 2018
Country/TerritoryGermany
CityDresden
Period8/02/189/02/18

Funding

Acknowledgments This research was partially funded by the Ministry of Science of Baden-Württemberg, Germany, for the Doctoral Program “Services Computing” (http://www.services-computing.de/?lang=en).

FundersFunder number
Ministry of Science of Baden-Württemberg

    Fingerprint

    Dive into the research topics of 'Analyzing the relevance of SOA patterns for microservice-based systems'. Together they form a unique fingerprint.

    Cite this