Skip to main content

Contracts Concepts

Motivation​

When splitting a codebase into multiple services, all services need to be able to deploy independently. However, how to ensure that each deployment will not impact the behavior of other services?

The proposed solution is to constrain every service to interact with other services through a system of contracts.

Each interaction between services is inherently asymmetric:

  • The provider is responsible for giving resources to other services
  • The consumers use resources given by the provider

Each service can be both a provider and a consumer for different contracts.

In order to make these contracts safe, each side of the contract must be able to validate it:

  • statically with Typescript
  • dynamically with JSONSchema

Defining contracts between services​

Serverless contracts are based on the idea of defining contracts before implementing them.

Check out how to use these contracts!

Securing the deploy process (beta)​

Serverless contracts enable validation at deploy time in order to prevent breaking changes to be deployed in production. See the Serverless-plugin (TODO) for more details on the available configuration and commands.