Microservice Architecture Practices and Experience: a Focused Look on Docker Configuration Files

TL;DR

This paper analyzes Docker configuration files to understand current microservice architecture practices, revealing diverse configurations and emphasizing the need for further industrial comparison to identify best practices.

Contribution

It introduces a mining software repositories approach to capture microservice practices through Docker configs, providing a detailed landscape overview.

Findings

Diverse Docker configurations observed across microservices

Current practices vary significantly in Docker setup

Further industrial studies needed for best practice identification

Abstract

Cloud applications are more and more microservice-oriented, but a concrete charting of the microservices architecture landscape -- namely, the space of technical options available for microservice software architects in their decision-making -- is still very much lacking, thereby limiting the ability of software architects to properly evaluate their architectural decisions with sound experiential devices and/or practical design principles. On the one hand, Microservices are fine-grained, loosely coupled services that communicate through lightweight protocols. On the other hand, each microservice can use a different software stack, be deployed and scaled independently or even executed in different containers, which provide isolation and a wide-range of configuration options but also offer unforeseeable architectural interactions and under-explored architecture smells, with such experience captured mainly in software repositories where such solutions are cycled. This paper adopts a mining software repositories (MSR) approach to capture the practice within the microservice architecture landscape, by eliciting and analysing Docker configuration files, being Docker the leading technical device to design for, and implement modern microservices. Our analysis of Docker-based microservices gives an interesting summary of the current state of microservices practice and experience. Conversely, observing that all our datapoints have their own shape and characteristics, we conclude that further comparative assessment with industrial systems is needed to better address the recurring positive principles and patterns around microservices.