Abstract (EN):
Although service-based architectures offer significant advantages, some aspects of service orchestration remain challenging, particularly for new adopters. Despite the availability of resources on orchestration techniques, many lack clarity or detail. As a result, best practices are often not well explained or standardized, making them difficult to implement and hindering broader adoption within the software industry. To address these concerns, we looked into existing literature and tools to identify common practices. We used our findings to describe as patterns two patterns focused on orchestration configuration, which we present in this paper, and that serve as a stepping stone for other orchestration practices: labeling and resource reserve and limit. These patterns contribute to configuring a system; the former consists of defining key-value pairs to express identifiable properties of system components, and the latter is about supporting two bounds for each resource type: the amount of resources reserved for the service to operate and the maximum amount of resources it can use.
Language:
English
Type (Professor's evaluation):
Scientific