Microservices is a buzzword and everyone is using it to modernize their company and themselves.

Add a cloud in the context and boom, you are equivalent of some Tech gaint.

Well then, if you say so why don't you implement or try to implement in proper way. Use the right tools, "opensource" if you have heard of it has a ton of stuff right for the job.

But no, all you do is write the same old services in Java, put a label of "cloud native" and stick it out so proudly that clients think "oh a new shiny thing".

Putting out poster of "Immediate job requiment for Microservices" and staring blank when the candidate tries to explain how the Microservices work, but you know only about EJBs and you are sitting in interview room wondering what he is really talking about. I dint hear a single word of Java because that is all I know. Then finally rejecting the candidate because he dint say EJB in the interview.

The point is, some shit people don't want to improve themselves nor let anyone improve. Fear of being replaced by a younger generation of developers has plauged the seniors in ways no one can think of.

Pain in an ass every time I have to work with EJB Service. :(

I had long time to figure out how to send an email via java over wildfly with @Resource annotation and finally found how to do it, according StackOverFlow, i just had to create new instance with @EJB Annotation instead create it with "new" *face palm*

RMI and EJB is soooo legacy, booooo

gRPC is sooooo new and cool

Why does EJB not allow me to access the methods. works, works, works for 3 methods and bam client access exception for the fourth one. Is there like a method count or something. I dunno if glassfish is unhappy for some reason. PermitAll, refershed Netbeans like a million times. I dunno could just use nodejs and javascript but project constraints.
Okay, enough for my first rant. I will debug away :(