Java enterprise software versus what it should be

Posted by lukaseder on Friday February 28, 2014 @08:21AM
from the obsidianscheduler.com dept.

http://www.obsidianscheduler.com/blog/java-enterprise-software-versus-what-it-should-be/

( 4 comments | 6 points | on HN )

Re:Java enterprise software versus what it should be by sorincos on Friday February 28, 2014 @09:19AM (#7318780)

An enticing title, a good introduction, then... I'm a bit disappointed. Now, the problem with an alternate setup like this isn’t necessarily the individual pieces of technology selected. I definitely have issues with some of the ones in the example, but the real issue is how the choices were made and what the motivations were for using certain technologies.

[ Parent | on HN ]

Re:Java enterprise software versus what it should be by lukaseder on Friday February 28, 2014 @09:38AM (#7318866)

It might be a bit promotional towards their own products, agreed. But it is just an example...

[ Parent | on HN ]

Re:Java enterprise software versus what it should be by fournm on Friday February 28, 2014 @11:23AM (#7319669)

What's certainly funny is that our current enterprise stack looks a lot more like what you lay out they "should" look like, and we're constantly looking for making it leaner.

That's kind of comforting, really.

[ Parent | on HN ]

Re:Java enterprise software versus what it should be by lukaseder on Friday February 28, 2014 @11:25AM (#7319676)

What particular elements are you having issues with? I.e. which parts aren't lean (yet) in your case?

[ Parent | on HN ]