I happened to reread part of an original EJB book, and with hindsight I am now wondering if EJB = microservice was the intended use. The app server would, on mu

I happened to reread part of an original EJB book, and with hindsight I am now wondering if EJB = microservice was the intended use. The app server would, on multiple machines, start and stop EJB instances like kubernetes does with node instances. The whole thing tries to hide there is a network in there, automagically connecting everywhere. Which would make the whole bloat thing moot and the whole EJB stack comically misused. But look at it as an EJB providing an interface to the outside world. Forget about making almost every class an EJB. Then the 2 styles start to look quite similar, especially if 'the network is the computer'. There were of course still plenty of bad design decisions. Every vendor has its own RMI variant, requiring drivers instead of a standardized http+json. 4 files for the interfacevis iver the top. The EJB database interface was bad.