We invite contributions related to, but not limited to,
* migration to a microservices architecture;
* microservices refactoring, evolution, and maintenance;
* autonomic computing with microservices;
* functional and nonfunctional requirements for microservices;
* designing for failure, repair, and recovery in microservices;
* architectural patterns and antipatterns for microservices;
* architecture conformance and evaluation for microservices;
* modeling languages for microservice design;
* container technology for microservices;
* unikernel microservices and serverless architectures;
* performance modeling, monitoring, evaluation, and capacity planning for microservices;
* microservices’ cultural aspects;
* agile development and microservices;
* DevOps and microservices;
* microservices for cloud-native architectures;
* privacy and security for microservices;
* microservices’ role in architecting big data systems;
* building user interfaces in a microservices architecture;
* SOA and microservices;
* decentralized governance and microservices; and
* the strengths, weaknesses, and challenges of implementing microservices in different application domains.

Because microservices research has been patchy, with few real experiences reported by companies such as Netflix and Thoughtworks, we specifically seek practical papers that could contribute to the software development and research communities by describing

* best practices and methodologies,
* tool support,
* empirical studies,
* industrial-scale case studies, and
* experience reports.

Experience reports don’t need to make an original research contribution but should present practitioners’ experience by describing aspects such as the microservices architecture used, challenges faced, solutions attempted, and results obtained.