Yaron Schneider

A default socket path is better.

> From the runtime perspective two major changes: > The runtime would not need to understand the concept of a pluggable component. It is totally agnostic to how processes start/run,...

Looks good.

> Existing components should be grandfathered in. We should make sure to revisit their certification tests when we have an opportunity to do so. > https://github.com/orgs/dapr/teams/approvers-components-contrib https://github.com/orgs/dapr/teams/maintainers-components-contrib should ensure that...

/ok-to-test

/ok-to-test

It'd be good to move to a maintained logger. Re: performance, we don't have any per-call logging in `info` mode but async logging might be helpful for our API event...

We can point users to use Consul in self hosted mode. Alternatively, if we find another cross machine self discovery mechanism that doesnt involve an external agent (as this is...

I don't support expanding the placement service to provide service discovery, although I am guilty of suggesting the same in the past. Assigning extra responsibilities for a component that is...

I do not support using Redis or any state store for service discovery purposes as that would create a tight coupling between a state store and a name resolution component....