Hacker News Reader

Comment by yummyfajitas | Hacker News Reader

The only punch line is "hey microservice hipsters, those uncool Enterprise Java guys already solved this problem."

Hasn't that been the punch line of the last 10 years of tech?

"Oh hey data hipsters, no I'm sorry our SQL data base is 200TB, no we don't have performance problems."

"Oh no we don't need your functional restless framework, we've been using a java framework for like 10 years, it peaks out at 1000 req/s."

"Why would we buy 4 webservers? It has 4 nics, and 8 CPU sockets. Sure it costs 500k each, but then we can keep using our java framework."

I find it useful to read articles by someone who will translate from hipster to crotchety-unix-grey-beard for me.

c2wiki does that for you ^-^

Yep, in the last few years I keep thinking, "Maybe it's time to get over my distaste for Java and just use it". They have some kind of type system, lots of pretty good tools (aside from Eclipse) and documentation for even the crappiest Java library is light years ahead of what you get with most JavaScript projects (even API docs for Java libs are easier to navigate and read!)

I guess. Though those Enterprise Java guys were using concepts developed in the '50s and '60s, well before Java existed. [1]

[1] https://en.wikipedia.org/wiki/Object-oriented_programming#Hi...

Every Java program becomes a bug ridden slow version of half of Common Lisp (implemented in xml)

Completely forgetting that application architecture and design is constrained by time and that those "uncool Entreprise Java guys" actually have much more time to work on "heavy" architectures compared to web services.

How do Service Objects require more time than microservices? If anything I've found they take less time - logically the code is similar to microservices and you need to spend less time on devops.

You're forced to explicitly define the interface. While I think the advantages of an explicit interface are well worth it, I can write a Javascript microservice with no defined interface faster than I can write an interface declaration + implementation in Scala.

We talking java beans. I think I used that first (and last) 15 years ago and it was ugly to work with.

Technically it's EJB (Enterprise Java Beans), JavaBeans is a pattern where you need to adhere to particular coding conventions (getters, setters, naming of said getters and setters).

I also used to work with these a long time ago (EJB 1.1 and 2.0). A lot has changed since then though, and EJB 3 has solved a lot of the pain points (arguably pushed by the success of concepts used in Spring and Hibernate, whose authors served in the JCP for the newer JEE specs).

Reply on news.ycombinator.com