Architecting Microservices: Practical Opportunities and Challenges

Baškarada, Saša; Nguyen, Van‐Dinh; Koronios, Andy

doi:10.1080/08874417.2018.1520056

Cited by 52 publications

(44 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Several empirical studies about challenges for the adoption of Microservices exist. Baškarada et al [12] conducted 19 indepth interviews with experienced architects. They discussed opportunities and challenges associated with the adoption and implementation of Microservices.…”

Section: Related Workmentioning

confidence: 99%

“…Especially large corporate systems of record like Enterprise Resource Planning (ERP) were not seen as appropriate targets. In this context, organizational challenges such as DevOps methodologies would be less serious for Information and Communication Technology enterprises than for traditional organizations, where IT was perceived as a "necessary evil" [12].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Assuring the Evolvability of Microservices: Insights into Industry Practices and Challenges

Bogner

Fritzsch

Wagner

et al. 2019

2019 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

While Microservices promise several beneficial characteristics for sustainable long-term software evolution, little empirical research covers what concrete activities industry applies for the evolvability assurance of Microservices and how technical debt is handled in such systems. Since insights into the current state of practice are very important for researchers, we performed a qualitative interview study to explore applied evolvability assurance processes, the usage of tools, metrics, and patterns, as well as participants' reflections on the topic. In 17 semi-structured interviews, we discussed 14 different Microservice-based systems with software professionals from 10 companies and how the sustainable evolution of these systems was ensured. Interview transcripts were analyzed with a detailed coding system and the constant comparison method.We found that especially systems for external customers relied on central governance for the assurance. Participants saw guidelines like architectural principles as important to ensure a base consistency for evolvability. Interviewees also valued manual activities like code review or boy scouting, even though automation and tool support was described as very important. Source code quality was the primary target for the usage of tools and metrics. Despite most reported issues being related to Architectural Technical Debt (ATD), our participants did not apply any architectural or service-oriented tools and metrics. While participants generally saw their Microservices as evolvable, service cutting and finding an appropriate service granularity with low coupling and high cohesion were reported as challenging. Future Microservices research in the areas of evolution and technical debt should take these findings and industry sentiments into account.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Assuring the Evolvability of Microservices: Insights into Industry Practices and Challenges

Bogner

Fritzsch

Wagner

et al. 2019

2019 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

show abstract

“…International Journal of Aerospace Engineering a lightweight communication mechanism to exchange data [30]. MSA allows the team to build services by using appropriate program languages and tools according to the business context, which has advantage over the monolithic architecture [31]. Although MSA and SOA exhibit some commonalities with respect to the definition and design, they also significantly differ, as shown in Table 1 [32].…”

Section: Microservice Architecture and Container Technologymentioning

confidence: 99%

“…In contrast, the highly cohesive and low-coupling MSA does not emphasize the ESB, which leads to more flexibility, enforceability, and scalability [34,35]. Another key difference is that most services in SOA are derived from monolithic architecture applications and functions, which cannot be changed, scaled, or deployed independently [31].…”

Section: Microservice Architecture and Container Technologymentioning

confidence: 99%

Microservice-Based Platform for Space Situational Awareness Data Analytics

Lan

et al. 2020

International Journal of Aerospace Engineering

View full text Add to dashboard Cite

The development, deployment, and maintenance of the current space situational awareness (SSA) information system have become increasingly complex. However, researchers cannot flexibly and conveniently apply the research results to practical applications due to the lack of basic research platforms for SSA. Inspired by X as a Service (XaaS), we propose the microservice-based platform for SSA data analytics to provide a scaffold-like platform for researchers. Based on microservice, the architecture for this platform is proposed to meet the requirements of flexible development and loosely coupled deployment. To facilitate the use of the platform, the hybrid data service layer is established to provide basic data for research and the functional service layer is designed to provide services for clients and applications. Due to the massive data processing requirements, the data analysis architecture and processing model, which can easily integrate various user-defined algorithms and significantly improve the computational efficiency, are proposed based on the Lambda architecture. To verify the platform's effectiveness, two cases are established and implemented. The results show that this platform can provide a convenient, flexible, and efficient platform for the requirements of algorithm integration, experiment, and data display from users and researchers.

show abstract

“…According to [12] concluded under the MSA architecture is the latest architectural trend which has significantly gained popularity over the past few years. Although there is a lot of hype associated with MSA, and while many vendors and enthusiasts promote various architectural benefits that are said to be related to MSA, with the exception of a small number of success stories that are often mentioned (for example, Amazon, Netflix, and Guardian).…”

Section: Fig 4 Microservices Approach Versus Traditional Applicationmentioning

confidence: 99%

Transforming the Monolith E-Procurement Application

Firmansyah*,

Ganeswangga,

Fajar

2019

IJITEE

View full text Add to dashboard Cite

 Abstract: Digital transformation in IT organizations needs to overcome a number of key challenges: (1) Costs of change, the customer wants to significantly reduce the cost of technology, and on the other hand the customer also does not want to fund technological changes that do not produce benefits for him directly. (2) Rate of change, customers request more frequent release cycles to compensate for changes in information and service requirements. (3) Quality of change, Increased application scalability. For that reason, IT organizations in making business changes need to do what needs to be modular in developing applications and deployments. Architectural Microservices (MSA) is an alternative architecture in building an application. The MSA conversion process can start patterns that are adapted to future needs. The release cycle is carried out by implementing automation for continuous delivery and continuous integration into continuous development, transforming data services into service forms, so as to answer the challenges of digital transformation. In this paper explains how to transform architects and their design in the E-Procurement application system using MSA.

show abstract

Architecting Microservices: Practical Opportunities and Challenges

Cited by 52 publications

References 18 publications

Assuring the Evolvability of Microservices: Insights into Industry Practices and Challenges

Assuring the Evolvability of Microservices: Insights into Industry Practices and Challenges

Microservice-Based Platform for Space Situational Awareness Data Analytics

Transforming the Monolith E-Procurement Application

Contact Info

Product

Resources

About