Remove the concept of deployments

[tillrohrmann]

Currently, a deployment couples the deployment of a set of components together with a fixed revision (version) which is determined at discovery time. This model is simple wrt to versioning of services because users don't have to think about it. However, it comes at a cost that one cannot have different physical deployments that serve a given revision. Moreover, there is currently no way to bring back an already decommissioned deployment because the assumption is that a deployment revision is monotonically increasing.

Instead, we want to allow endpoints to tell which revision of a component they are serving. Thereby we decouple the deployment of an endpoint from its version and allow adding components of a given version at a later point. What this means for the internal metadata is that we'll introduce a many-to-many relationship between components and endpoints. Moreover, we have to introduce the concept of a version/revision to the SDKs since the SDK need to tell the runtime about which revision of a component they are running.

Tasks

Beta Give feedback

1. Replace deployment with n:m mapping between components to endpoints
2. Update TS SDK to specify revision
3. Update Java SDK to specify revision