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.
Actually, in a way it is sort of sad how unfamiliar we are of the “previous generation’s” solutions. It’s not like load balancing, zero downtime, RPC and scaling are new things.
Simple code turned into a complete dependency injection spagetti just beacuse CDI was a specification and advertised as the next best thing to come from the Java EE ecosystem.
I am really glad we moved away from that area.
For us, it was good that Oracle stopped being invovled with Java EE. That allowed us to convince others in our team to move on to much simpler application development using core Java.
I had stopped paying attention to this Java EE/Jakarta EE area after the unnecessary drama that ensued in the community lead by an ex-Oracle employee.
I'm really surprised that Jakarta EE is still a thing.