Conversation Types

Caires, Luís; Vieira, Hugo Torres

doi:10.1007/978-3-642-00590-9_21

Cited by 49 publications

(50 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…OpenAPI) provide a foundation for tools that check contracts between services [32], even at the semantic level [37]. Also, formal approaches applying behavioural types and static type checking ensure the soundness of service interfaces [9], even in a multiparty setting. None of the above accounts for evolution and adaptation of service contracts.…”

Section: :26mentioning

confidence: 99%

“…New contract management methods, that include fine-grained ownership models for services, defining responsibilities of teams over modules, are needed to keep everything in sync and evolve seamlessly. Having a common specification for service contracts is paramount, allowing for the safety of service-based architectures to be checked a priori [9,38].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Robust Contract Evolution in a TypeSafe MicroServices Architecture

Seco

Ferreira²,

LourenÃ§o³

et al. 2020

Programming

View full text Add to dashboard Cite

Microservice architectures allow for short deployment cycles and immediate effects, but offer no safety mechanisms for service contracts when they need to be changed. Maintaining the soundness of microservice architectures is an error-prone task that is only accessible to the most disciplined development teams. The strategy to evolve a producer service without disrupting its consumers is often to maintain multiple versions of the same interface and dealing with an explicitly managed handoff period and its inherent disadvantages.We present a microservice management system that statically verifies service interface signatures against their references and supports the seamless evolution of compatible interfaces. We define a compatibility rela-tion�on types that captures real evolution patterns and embodies known good practices on the evolution of interfaces. Namely, we allow for addition, removal, and renaming of data fields of a producer module without breaking or needing to upgrade consumer services. The evolution of interfaces is supported by runtime generated proxy components that dynamically adapt data exchanged between services to match with the statically checked service code.The model proposed in this paper is instantiated in a core programming language whose semantics is defined by a labelled transition system and a type system that prevents breaking changes from being deployed. Standard soundness results for the core language entail the existence of adapters, and hence ensure the absence of adaptation errors and the correctness of the management model. This adaptive approach allows for gradual deployment of modules, without halting the whole system and avoiding losing or misinterpreting data exchanged between system nodes. Experimental data shows that an average of 57% of deployments that would require adaptation and recompilation are safe under our approach. ACM CCS 2012Software and its engineering → Development frameworks and environments; Software creation and management; Software evolution; Applied computing → Service-oriented architectures; Theory of computation → Semantics and reasoning; Development Environment (Module + Signature) Development Environment (Module + Signature) Development Environment (Module + Signature) Local Deployment Manager Local Deployment Manager Local Deployment Manager Local Deployment Manager Definitions Product k1 : {Id k2 : int, Name k3 : string, Amount k4 : int, Discount k5 : int} Get k6 : (id : int) → Product = {Id k2 = 1, Name k3 = "H DD", Amount k4 = 99, Discount k5 = 0} Save k7 : (p : Product) → string = "OK" Catalog V 1 Definitions Promote k8 : (p : Product) → Product = p {Name k3 = p.Name + "(Sale)", Discount k5 = 5} Reference to Catalog Product k1 : {Id k2 : int, Name k3 : string, Amount k4 : int, Discount k5 : int} Marketing V 1 Definitions Improve k9 : (id : int) → string = Save(Promote(Get(id))) Reference to Catalog Product k1 : {Id k2 : int, Name k3 : string, Amount k4 : int, Discount k5 : int} Get k6 : int → Product Save k7 : Product → string Reference to Mark...

show abstract

Section: :26mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Robust Contract Evolution in a TypeSafe MicroServices Architecture

Seco

Ferreira²,

LourenÃ§o³

et al. 2020

Programming

View full text Add to dashboard Cite

show abstract

“…The conversation calculus (see [CV09] and the references there) organizes behaviour around places of conversation, which slightly resemble Boxed Ambients [BCC04]. The conversation types record the overall behaviour of processes and assure progress, while accounting for dynamical join/leave of a possibly unanticipated number of participants.…”

Section: Conversation Calculusmentioning

confidence: 99%

“…An example of [CV09] showing how the conversation calculus takes advantage of localities is the following composition of two conversation contexts, named Buyer and Seller :…”

Section: Conversation Calculusmentioning

confidence: 99%

Sessions and Session Types: An Overview

Dezani‐Ciancaglini

de’Liguoro

2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. We illustrate the concepts of sessions and session types as they have been developed in the setting of the π-calculus. Motivated by the goal of obtaining a formalisation closer to existing standards and aiming at their enhancement and strengthening, several extensions of the original core system have been proposed, which we survey together with the embodying of sessions into functional and object-oriented languages, as well as some implementations.

show abstract

“…Multiparty sessions [14] generalise session types to support more than two participants; they have been used in [9] to statically compute upper bounds of the size of buffers used for asynchronous communications in global interactions. Moreover, dynamic multiparty sessions have been studied in [6] and [7]. On top of multiparty sessions, in [4], a theory of design-by-contract for distributed interactions has been introduced.…”

Section: Introductionmentioning

confidence: 99%

A Modular Toolkit for Distributed Interactions

Lange

Tuosto

2011

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

We discuss the design, architecture, and implementation of a toolkit which supports some theories for distributed interactions. The main design principles of our architecture are flexibility and modularity. Our main goal is to provide an easily extensible workbench to encompass current algorithms and incorporate future developments of the theories. With the help of some examples, we illustrate the main features of our toolkit.

show abstract

Conversation Types

Cited by 49 publications

References 18 publications

Robust Contract Evolution in a TypeSafe MicroServices Architecture

Robust Contract Evolution in a TypeSafe MicroServices Architecture

Sessions and Session Types: An Overview

A Modular Toolkit for Distributed Interactions

Contact Info

Product

Resources

About