[metapsj]

imho the key concept is in-process rest as in representational state transfer as an interface. instead of an imperative interface it's more of a protocol based interface. think http middleware built around a standard interface like ruby's rack, asp.net's owin, or python's wsgi. once you have that style of abstraction it becomes pluggable and you can chain them together.

here's a past discussion on in-process rest.

https://news.ycombinator.com/item?id=21560626

[magicalhippo]

Thanks, that's a bit more specific.

Think I'd have to play with it to see how it really differed from my normal composition of interfaces and implementations.