Agility with Microservices Programming 2025
Scope
Agile architecture does not necessarily emerge from the use of agile development practices, it needs to be deliberately sought after. This often means creating systems as sets of small, independent components that collaborate to provide the desired functionality. Such components are usually loosely-coupled and expose well-defined APIs that are accessible over standard communication protocols and data formats—they can be individually developed and tested, they can be easily replaced by alternative implementations if needed, and they provide great flexibility when deploying and scaling the system.
This style of architecture is often described as microservices. Essentially, microservices decompose a system into an architecture of standalone modules that (i) are simpler to maintain and evolve; (ii) scale efficiently; and (iii) can be reused as building blocks for other architectures. Transitioning to a microservice architecture is crucial for companies in highly-competing markets, where agility and flexibility of software systems become a critical asset to establish leadership.
However, microservices also come with new challenges. Such distributed architectures are complex to design and require substantial expertise. Companies that decide to adopt them will need to adapt their standards, practices, and processes. Furthermore, the introduction of microservices often slows down development, particularly during the migration from a monolithic architecture. Yet, transitioning to microservices is crucial for companies in highly competitive markets, where the agility and flexibility of software systems and their development become critical assets to establish leadership. In the era of AI-based systems and LLMs, microservices play a pivotal role in building reliable and scalable systems that meet the requirements of such data-intensive applications. AI-assisted architecting, development, and refactoring can help to design new microservices-based systems or modernize monolithic legacy applications efficiently.
The Workshop on Agility with Microservices Programming (AMP) aims to collect experiences and studies on microservice architectures, share best practices, report on failure cases, and build a community knowledge base. The fifth edition of AMP aims to continue the success of its previous editions:
AMP2023 (co-located with ECSA 2023)
AMP2022 (co-located with XP 2022)
AMP2021
AMP2020
Theme and Topics
Transitioning to microservices-based architectures is crucial for companies in highly competitive markets, where the agility and flexibility of software systems are essential. Microservices as an architectural style facilitate agility, streamline integration and enable more flexible solutions. However, an adoption also increases complexity and requires novel software construction techniques and advanced agile engineering practices. Especially since the rise of large language models (LLMs), development practices increasingly incorporate AI tools, opening a new field of challenges and opportunities for microservices programming.
The AMP workshop aims to collect experiences on microservice adoption and reporting best practices, as well as failure cases, to build community knowledge based on past mistakes and successes. We seek to collect original work on the science and engineering of programming microservices, including but not limited to evolutionary and agile architectures, methods and tools, patterns, operational practices and DevOps, agile teams, programming languages and techniques for microservices, software quality aspects, metrics and software analytics, verification, test-driven approaches and testing, architectural refactoring, empirical studies, and experience reports on microservices adoption and teaching. We also emphasize the current trend towards AI-driven software engineering practices and the development of data-intensive applications. The workshop seeks for solutions and experiences both on AI-assisted tooling, and building data-intensive applications and LLMs using microservices. The workshop is open to experience reports from practitioners and academics. We seek to collect original work on the science and engineering of programming microservices, including but not limited to the following topics:
- Software engineering methods and tools for microservices
- Enable an evolutionary and agile architecture with microservices
- Microservices in the context of AI-based data-intensive applications and LLMs
- Microservices for machine learning model operation management (MLOps)
- AI-enhanced development and refactoring of microservices-based systems
- Programming languages, techniques, and design patterns for microservices
- Operations practices for microservices and DevOps support
- Organizational dynamics and practices of agile teams working with microservices
- Software Quality, metrics, and analytics in microservice architectures
- Testing, verification, and test-driven development for microservices
- Architecture recovery and documentation strategies for microservices
- Refactoring in the context of microservice architectures
- Empirical studies and experience reports on microservices
- Teaching and learning microservices: education strategies and experiences
AMP 2025 is organized with the official support of the Microservices Community, an international non-profit organization interested in sharing knowledge and fostering collaborations about the paradigm of microservices.
Contributions and Evaluation
AMP 2025 seeks original contributions of the following types (maximum length):
- Full papers: research papers, industry case studies (between 8 and 16 pages in LNCS format, incl. references, single-blinded).
- Extended Abstracts: tool presentations, position papers (2 to 4 pages, including references, will not appear in the proceedings)
Papers should be formatted in Springer’s LNCS format and submitted through EasyChair
In accordance with ECSA 2025 publication guideline for workshops, accepted papers will be published in the post-proceedings.
How to submit
Contributions should be formatted in Springer LNCS format and submitted through EasyChair (link below) as a PDF file interpretable by common PDF tools and printable in black and white on A4 paper.