Re:Microservices and the First Law of Distributed Objects
by djur on Wednesday August 13, 2014 @09:28PM
(#8175696)
I 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.
Re:Microservices and the First Law of Distributed Objects
by CMCDragonkai on Wednesday August 13, 2014 @07:20PM
(#8175440)
Isn't that kind of like erlang?
Re:Microservices and the First Law of Distributed Objects
by AdrianRossouw on Wednesday August 13, 2014 @11:29PM
(#8175953)
it's very much like that. and erlang has proved that it's a valid approach.
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.