Configuring Cloud-Service Interfaces Using Flow Inheritance

TL;DR

This paper introduces a novel automatic interface configuration mechanism for cloud services that emphasizes data format compatibility and flow inheritance, enabling flexible, reusable, and provably consistent service compositions without behavioral contracts.

Contribution

It proposes a new approach that automatically derives service interfaces focusing on data formats and flow inheritance, unlike existing methods that rely on behavioral contracts.

Findings

Automatic interface derivation from code

Supports flow inheritance and subtyping

Ensures global consistency without source security issues

Abstract

Technologies for composition of loosely-coupled web services in a modular and flexible way are in high demand today. On the one hand, the services must be flexible enough to be reused in a variety of contexts. On the other hand, they must be specific enough so that their composition may be provably consistent. The existing technologies (WS-CDL, WSCI and session types) require a behavioural contract associated with each service, which is impossible to derive automatically. Furthermore, neither technology supports flow inheritance: a mechanism that automatically and transparently propagates data through service pipelines. This paper presents a novel mechanism for automatic interface configuration of such services. Instead of checking consistency of the behavioural contracts, our approach focuses solely on that of data formats in the presence of subtyping, polymorphism and flow inheritance. The paper presents a toolchain that automatically derives service interfaces from the code and performs interface configuration taking non-local constraints into account. Although the configuration mechanism is global, the services are compiled separately. As a result, the mechanism does not raise source security issues despite global service availability in adaptable form.