dzmitry-lahoda

if you are ok to consider to remove alias, than i am ok. at least as feature. read is as k8s labels and selectors.

``` Check if alias resolves to the old service Deploy new service Migrate data Add alias to the new service Remove old service (not just alias - why leave service...

but yeah, for now will loop over services, find aliased, find id and remove services. also it would be shorter to remove alias. i do not care of garbage. GC...

i saw it. there is bug. 4 services under same alias. via srv call to show services.

so it not removed for some reason.

need both store and query (start from subset of queries)

if ceramic can do same or similar - than could we have ceramic build in?

allow to express enums in aqua and force reduce cardinality onto parameters, same as dht - peer id and service id any, other parametes with cardinality of 666 max.

nope, ceramic does not suits. need realtime compressed cheap histograms built in

than info can be used for routing, circuit breakers, pricing.