The athletic heart syndrome in web service evolution

Abstract

Despite the particular standards, technologies, and trends (W3C, RESTful, microservices, etc.) that a team decides to follow for the development of a service‐oriented system, most likely the team members will have to use one or more services that solve general‐purpose problems like cloud computing, networking and content delivery, storage and database, management and governance, and application integration. Typically, general‐purpose services are long‐lived, they have several responsibilities, their interfaces are complex, and they grow over time. The way that these services evolve also affects the evolution of any system that will depend on them. Consequently, the selection of the particular services that will be used is a main concern for the team. In this paper, we report a pattern, called the athletic heart syndrome, which facilitates the selection of services that evolve properly. Patterns specify best practices that emerge from multiple real‐world cases. In our context, the athletic heart syndrome comes out from a study that concerns the evolution of a set of popular, long‐lived Amazon services that cover different domains. According to the athletic heart syndrome, the developers should select services whose heartbeat of changes looks like the heartbeat of an athlete when he is at rest. Specifically, the heartbeat of changes should consist mostly of calm periods, interrupted by few spikes of change. Similarly, the incremental growth of the services should involve mainly calm periods of maintenance, separated by spikes of growth. Selecting services that adhere to the pattern signifies high chances that the services evolve to deal with changing requirements. The pattern further guarantees that the service evolution involves both the expansion of the services with new functionalities and the maintenance of existing ones. The pattern also assures that the complexity increase in the service interfaces will be smooth and tolerable. Finally, conformance with the pattern implies that the growth of the services will be predictable.

An Internet‐of‐Disease System for COVID‐19 Testing Using Saliva by an AI‐Controlled Microfluidic ELISA Device

“…A MySQL database had also been configured as the Amazon RDS in the server PC. [ 52 ] This server PC had been employed as the main cloud storage of the IoD system. For the data visualization in the application layer, the Python Django environment had been installed in the server PC that had been configured as the EC2 environment of the Amazon Web Service (AWS).…”

“…For better data management, an API had been created using Django REST framework‐based API gateway that had used a gateway scheme like Amazon's HTTP signature scheme providing a high level of availability, privacy, security, and robustness. [ 52 , 54 ] An AJAX layer had been created to communicate with the IoD platform user interface using the JavaScript AJAX library that had translated Semantic Web data into machine‐readable data. [ 55 ] The front‐end design of the IoD user interface had been structured using HTML, and CSS.…”

About the special issue on: “Distributed Complex Systems: Governance, Engineering, and Maintenance”

“…The contribution “ The Athletic Heart Syndrome in Web Service Evolution ” 7 studies how web services evolve and how such evolution also affects the evolution of any system that will depend on them. In this context, the work discusses a pattern (i.e., the athletic heart syndrome pattern) which aims to facilitate the selection of services that evolve properly.…”