Open Stack

> Up to this point, projects have interfaced with each other via HTTP
> APIs. It seems much easier to replace a project with an alternate
> implementation using HTTP based interfaces than one that presents the
> equivalent of our home-grown rpc communication. I'm concerned about a
> future where projects become more tightly coupled due to rpc
> communications as opposed to HTTP APIs.

Except we have certain scale and availability characteristics around RPC that don't apply natively to HTTP and specifically not to our HTTP servers or clients. There is nothing that would prevent us from supporting an HTTP-based "rpc" driver, if the low-level protocol is a problem.

I think the problems with using and maintaining RPC compatibility across projects is of a greater concern than if there is an API to allow it.

Regards,
Eric Windisch