Conference
Managing API Evolution in Microservice Architecture.
| Τίτλος: | Managing API Evolution in Microservice Architecture. |
|---|---|
| Συγγραφείς: | Lercher, Alexander |
| Πηγή: | ICSE: International Conference on Software Engineering; 2024, p195-197, 3p |
| Θεματικοί όροι: | Application program interfaces, Computer architecture, Scalability, Software maintenance, Software reliability |
| Περίληψη: | Nowadays, many software systems are split into loosely coupled microservices only communicating via Application Programming Interfaces (APIs) to improve maintainability, scalability, and fault tolerance. However, the loose coupling between microservices provides no immediate feedback on breaking API changes, and consuming services break or exhibit unexpected behavior only after the first actual call to the changed API. Hence, development teams must actively identify and communicate all breaking changes to affected teams to stay compatible. This research addresses this problem with three contributions. First, we identified API evolution strategies and open challenges in practice with an explorative study. Based on the study findings, we formulated two open research directions for evolving publicly accessible APIs, i.e., REpresentational State Transfer (REST) APIs. As the second contribution, we will introduce a REST API change extraction approach to improve the change notification accuracy. We plan experiments on open-source projects to evaluate our approach's accuracy and compare it to openapi-diff for structural changes. Third, we plan to investigate methods for automating communication with affected teams, which will then improve the change notification reliability. Finally, we will evaluate the accuracy and reliability of our notifications with a user study. [ABSTRACT FROM AUTHOR] |
| Copyright of ICSE: International Conference on Software Engineering is the property of Association for Computing Machinery and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Βάση Δεδομένων: | Complementary Index |
| FullText | Text: Availability: 0 |
|---|---|
| Header | DbId: edb DbLabel: Complementary Index An: 185196542 RelevancyScore: 945 AccessLevel: 6 PubType: Conference PubTypeId: conference PreciseRelevancyScore: 945.330749511719 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: Managing API Evolution in Microservice Architecture. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22Lercher%2C+Alexander%22">Lercher, Alexander</searchLink> – Name: TitleSource Label: Source Group: Src Data: ICSE: International Conference on Software Engineering; 2024, p195-197, 3p – Name: Subject Label: Subject Terms Group: Su Data: <searchLink fieldCode="DE" term="%22Application+program+interfaces%22">Application program interfaces</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+architecture%22">Computer architecture</searchLink><br /><searchLink fieldCode="DE" term="%22Scalability%22">Scalability</searchLink><br /><searchLink fieldCode="DE" term="%22Software+maintenance%22">Software maintenance</searchLink><br /><searchLink fieldCode="DE" term="%22Software+reliability%22">Software reliability</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: Nowadays, many software systems are split into loosely coupled microservices only communicating via Application Programming Interfaces (APIs) to improve maintainability, scalability, and fault tolerance. However, the loose coupling between microservices provides no immediate feedback on breaking API changes, and consuming services break or exhibit unexpected behavior only after the first actual call to the changed API. Hence, development teams must actively identify and communicate all breaking changes to affected teams to stay compatible. This research addresses this problem with three contributions. First, we identified API evolution strategies and open challenges in practice with an explorative study. Based on the study findings, we formulated two open research directions for evolving publicly accessible APIs, i.e., REpresentational State Transfer (REST) APIs. As the second contribution, we will introduce a REST API change extraction approach to improve the change notification accuracy. We plan experiments on open-source projects to evaluate our approach's accuracy and compare it to openapi-diff for structural changes. Third, we plan to investigate methods for automating communication with affected teams, which will then improve the change notification reliability. Finally, we will evaluate the accuracy and reliability of our notifications with a user study. [ABSTRACT FROM AUTHOR] – Name: Abstract Label: Group: Ab Data: <i>Copyright of ICSE: International Conference on Software Engineering is the property of Association for Computing Machinery and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.) |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=edb&AN=185196542 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1145/3639478.3639800 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 3 StartPage: 195 Subjects: – SubjectFull: Application program interfaces Type: general – SubjectFull: Computer architecture Type: general – SubjectFull: Scalability Type: general – SubjectFull: Software maintenance Type: general – SubjectFull: Software reliability Type: general Titles: – TitleFull: Managing API Evolution in Microservice Architecture. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: Lercher, Alexander IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 05 Text: 2024 Type: published Y: 2024 Titles: – TitleFull: ICSE: International Conference on Software Engineering Type: main |
| ResultId | 1 |