Hacker News Reader

Microservices today have all the same problems as OOP, but vastly amplified. My kingdom for some more functional approach to architecture, with services as more or less pure functional transforms, and some sort of extremely well-typed data mesh underneath.

The world runs on microservices, government, agencies, companies, departments, bodies, organs, cells.

Sure, reality has problems, and no it won't be solved by trying to understand everything as functions. Welcome to the world

Smalltalk is a partially-functional language (first-class functions in 1976, inspired by lisp) and also got static typing extensions many years ago.

Well...his original vision was communicating computers, and then scaling that down.

Except that Microservices tend to use REST (or something roughly like it) and not CORBA.

https://blog.metaobject.com/2019/11/what-alan-kay-got-wrong-...

Or signal, receptor, effector

https://en.wikipedia.org/wiki/Cell_signaling

The more I see how microservices evolve the more I think about J2EE remote objects / ejb. A little personal facepalm moment.