3 ms·
This is the spirit of microservices to me : https://news.ycombinator.com/item?id=7874317 https://news.ycombinator.com/item?id=7874317 "Instead of pretending e
by AdrianRossouw 12y ago
This is the spirit of microservices to me :
https://news.ycombinator.com/item?id=7874317 https://news.ycombinator.com/item?id=7874317
"Instead of pretending everything is a local function even over the network ...,
what if we did it the other way around?
Pretend your components are communicating over a network even when they aren't?"
-- Solomon Hykes (of Docker fame) on LibChan
To me, it's pretty much anti-OO, and that's why I find it refreshing.
- CMCDragonkai 12y agoIsn't that kind of like erlang?
- AdrianRossouw 12y agoit's very much like that. and erlang has proved that it's a valid approach.
- angersock 12y agoYep. All the distributed systems I've worked with devolve into a bad reimplementation of part of Erlang.
- djur 12y agoI don't see what's anti-OO about that. You have message passing (over the network) and encapsulated state. The actor model, in the large, resembles an idealized object system a lot more than an idealized functional system. Network access (and file I/O, etc.) is inherently impure. Pure functional style requires you to work around that, and async/message-passing approaches are an effective workaround. But the fact that functional languages funnel you into async doesn't make classical Smalltalk-style OO any less well-suited for async.