alt Hacker News> OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things.
This sounds a lot like microservice architecture.
Replies
Twey • today at 10:55 AM
Taken to an extreme. It's not feasible with current microservice architecture to, for example, represent every Boolean in the program as a service.
➕ show 1 reply
TZubiri • today at 9:46 AM
I too think that microservices and REST are Kay OOP, although through a network boundary of course
The separation of objects and usage of network protocols naturally forces interaction via communication and not data sharing, so perhaps as an emergent phenomenon it converges on Kay OOP. Although no doubt Netflix Microservice OG engineers were influenced by both Kay and Java.
Very similar, yes.
Except that Kay did not envision the distinct computers communicating via REST.
https://blog.metaobject.com/2019/11/what-alan-kay-got-wrong-...
Also: microservices currently require at least process and frequently even VM/Container/Machine boundaries.
In-Process REST scales that down:
https://link.springer.com/chapter/10.1007/978-1-4614-9299-3_...
Language support for In-Process REST:
https://dl.acm.org/doi/10.1145/3359591.3359729
https://objective.st/