Schema Evolution

architecture of geometry at glass window - monochrome
Posted by
architecture of geometry at glass window - monochrome

Vendia Share allows users to share a single source of truth in a secure and scalable manner through Universal Applications (Unis). Unis are automatically created using a user-supplied data model. Vendia Share takes the user supplied data model and deploys a Uni in a matter of minutes. This includes provisioning fully managed, fullly functional GraphQL APIs to interact with the Uni and a serverless distributed ledger that keeps data consistent across all participants.

As Uni participants grow and as the fidelity of solutions increase over time, it’s common for users to want to evolve the original data model used to create the Uni. Historically, there was no way for users to change the data model once a Uni was created. Any data model change to a Uni required destroying it and its accompanying nodes and recreating it with the new model.

This process was painful for users. Recreating a data model involves Vendia Share creating new cloud resources. This, in turn, means node GraphQL endpoints, S3 bucket ARNs, SNS topics change. Any integrations that interact with those resources need to be updated. During the development process this can introduce a lot of friction to developers and operators.

We’re very pleased to share that Vendia now allows developers to evolve a Uni’s data model. This change allows users to manage their Uni’s evolution without requiring changes to the Uni’s interfaces (e.g. a new GraphQL URL). Not only does this empower Vendia Share users, it also allows users the agility to evolve as business or participant needs change.

What sort of data model changes can be introduced? In short, additive or non-breaking changes can be made.

  • New types and their associated properties can be added
  • New properties of an existing type can be added
  • New enum values of an existing property can be added

What sort of changes cannot be introduced? In short, destructive or breaking changes.

  • Existing types cannot be removed
  • Existing properties cannot be removed
  • Type changes to existing properties cannot be changed
  • Required flag for an existing property cannot be changed

Let’s explore how to go through the process. You’ll need to have a Vendia user. If you haven’t already created one you can sign up at

Create a New Uni

The first step in our process is to create a new Uni. This example will use the Product database template.


You can create a single node in a supported region for the purposes of this example. After several minutes you should have a new Uni up and running.


Verify the Initial Schema

We can view the deployed schema from the Vendia Share web application.Default product demo schema

Though the schema is valid – our Uni was successfully created after all – it’s lacking something. It’s missing a quantity field to capture the count of each item we have in stock. The field isn’t available when we try to add a new product via the add_Product operation.


Let’s fix that problem.

Evolving the Schema

We can update our Uni’s existing data model to include a new property – quantity. We will use the new schema below.

NOTE: Make sure to save the schema below as evolved-schema.json.Evolved product demo schema

We can use the Vendia Share CLI to instruct the Share service to apply the new data model to our existing Uni.

share uni evolve --uni your-uni-name \
--schema evolved-schema.json

You should receive the following output from the above command: Schema evolution initiated

You Uni will move to an Updating state while the new schema is applied. Read requests of the Uni will succeed. Any write requests will be queued until the update is complete.


Verifying Results After Schema Evolution

Once your Uni enters a Running state you can begin working with your updated data model.


Let’s first make sure our new field – quantity – is present in our Uni’s schema.


Now that we know our new field is present, let’s confirm it’s accessible. We can go back to the node’s GraphQL Explorer and examine the available fields when running a add_Product operation.


We can now make use of quantity in our evolved schema.


Data models can change over time. Schema evolution in Vendia Share allows customers to make changes to their schemas without introducing additional complexity all while allowing them to focus on building innovative solutions.