Authors:
Nane Kratzke
and
Peter-Christian Quint
Affiliation:
Lübeck University of Applied Sciences, Germany
Keyword(s):
Microservice, Container, Docker, Cluster, Network, Performance, Reference, Benchmark, REST, SDN.
Related
Ontology
Subjects/Areas/Topics:
Cloud Applications Performance and Monitoring
;
Cloud Computing
;
Cloud Computing Enabling Technology
;
Collaboration and e-Services
;
Data Engineering
;
Development Methods for Cloud Applications
;
e-Business
;
Enterprise Information Systems
;
Mobile Software and Services
;
Ontologies and the Semantic Web
;
Performance Development and Management
;
Platforms and Applications
;
Services Science
;
Software Agents and Internet Computing
;
Software Engineering
;
Software Engineering Methods and Techniques
;
Telecommunications
;
Web Services
;
Wireless Information Networks and Systems
Abstract:
Companies like Netflix, Google, Amazon, Twitter successfully exemplified elastic and scalable microservice
architectures for very large systems. Microservice architectures are often realized in a way to deploy services
as containers on container clusters. Containerized microservices often use lightweight and REST-based mechanisms.
However, this lightweight communication is often routed by container clusters through heavyweight
software defined networks (SDN). Services are often implemented in different programming languages adding
additional complexity to a system, which might end in decreased performance. Astonishingly it is quite complex
to figure out these impacts in the upfront of a microservice design process due to missing and specialized
benchmarks. This contribution proposes a benchmark intentionally designed for this microservice setting. We
advocate that it is more useful to reflect fundamental design decisions and their performance impacts in the
upfront of a microservice
architecture development and not in the aftermath. We present some findings regarding
performance impacts of some TIOBE TOP 50 programming languages (Go, Java, Ruby, Dart), containers
(Docker as type representative) and SDN solutions (Weave as type representative).
(More)