Michael Griggs commented on IGNITE-6069:

The use-case for multiple versions of service active at one time is as follows:
 # Central Team creates a service that provides functionality
 # Application Team 1 accesses that service to use functionality
 # Application Team 2 accesses that service to use functionality
 # Central team needs to modify the service to improve functionality
 # Application Team 1 updates its code to use improved functionality, but 
Application Team 2 does not have time do so. If multiple active Service 
versions are not available, the Central Team can only evolve the functionality 
at the pace of the slowest Application Team. Multiple active service versions 
removes that limitation.

> Service versioning
> ------------------
>                 Key: IGNITE-6069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6069
>             Project: Ignite
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 2.1
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>            Priority: Major
> Make services upgradable -again-. 
> Main points:
> - compute binary type ID by (classname + version)
> - use serialVersionUuid as version ( ?)
> - all service instances with the same name must have the same version
> - make ServiceProxy aware of versions and upgrade process, pause requests 
> while service is being upgraded
> - extend Service interface (UpgradableService?) - add ability to collect 
> state of previous version before start.
> Once the feature is implemented, it has to be documented extensively. The 
> ticket must not be closed until this happens.

This message was sent by Atlassian JIRA

Reply via email to