v0.11.2

Services

Service Versioning

Changing the interface

Class name

As a service is internally named through its interface's class name (including package), we need to keep it stable. We can change it, as long as we use the @Name annotation to ensure that the internal name does not change. For example,

can be changed to:

We recommend always using a @Name annotation - with a simple name - for all services, to avoid keeping legacy names like here.

Method name

As a task is named through its interface's method name, we need to keep it stable. We can change also it, as long as we use the @Name annotation to ensure that the internal name does not change. For example:

can be changed to:

Method parameters

When a method is dispatched, its parameters are serialized and transported through Pulsar up to a Service worker. There, the parameters are deserialized and applied to an implementation of the service's method.

To guarantee that there is no discrepancy between the "caller" (the workflow) and the "receiver" (the service's method),

The signature of a task must not change.

And if the only parameter is of object type (which is recommended):

Any properties we add to this object type must have default values.

Method return value

when a workflow runs through a task already completed, it gets the return value by deserializing data from the workflow history. To guarantee that there is no discrepancy between the "sender" (the service's method) and the "receiver" (the workflow),

The return type of a task can not change.

And if the return type is an object (which is recommended):

Any properties we add to the return type must have default values.

Changing the implementation

As long as we follow the above recommendations to modify their interfaces, the implementation itself of the services can be modified without any particular constraints.

Previous
Service Syntax

New version 0.11.2!