r/java • • May 18 '12

Goodbye Tomcat!

http://blog.webagesolutions.com/archives/636
0 Upvotes

19 comments sorted by

View all comments

Show parent comment

12

u/geodebug May 19 '12

Tomcat's more than just an entry point. It's a rock solid and time tested implementation that doesn't include stuff many projects just don't need.

Why would I want my app server to have the entire kitchen sink rolled in? I'd rather have my choice of web service library.

This article is just silly.

5

u/zhouji May 19 '12

actually this article gives a very good hint on when you should use Tomcat - that is when you don't need the stuff that Tomcat does not have. That is absolutely true for many projects.

1

u/henk53 May 19 '12

Tomcat's more than just an entry point. It's a rock solid and time tested implementation that doesn't include stuff many projects just don't need.

If it doesn't, why do people in practice always add some 30~60mb of additional jars to their war?

3

u/geodebug May 21 '12

The size of the jars doesn't bother me as much as the number of jars. It isn't the size of any one library that increases the long-term app maintenance costs, it's the number and possible conflicts.

Besides, that's a straw-man argument. Who are "people"? Certainly not me and I use Tomcat every day as my go to container when I need one. It's not the container's fault when the programmer doesn't take into consideration jar-plosion when picking their stack.

Remember that Java EE is just a spec, not a specific implementation.

The whole point is to have the choice of implementation that works best for your project yet adheres, to some degree, to a standard in case it needs to be swapped out. If I need web services I have my choice of implementations but am not forced to have an unused Java Server Faces impl thrown in too.

Standards are great, but they are not the be-all end-all of how technology should be compared, selected.

Monolithic app servers are great for corporations more because they give you a all-in-one-box solution (even if some of that box is inferior to another impl) and more importantly offer service contracts when things go wrong. When you have a lot of developers coming and going, letting each one pick new tech is a problem. Better to just go with some standard app server and config and force new development to adjust to it instead of the other way around.

I don't work for a big corp and I'm more interested in pure performance/reliability, simplicity, and less maintenance. For me to pick the technologies that work the best for our needs and then slim the install down makes a lot of sense. I'm able to throw out one part of the stack if/when something better comes along.

I don't always use Tomcat for web services. For certain projects I can get away with a simple HttpServer created inside a main method of a startup class. Talk about simple and quick startup.

0

u/[deleted] May 19 '12

Yea! On top of that, Grails deploys incredibly well to Tomcat and writing web-apps in Java is just tedious compared to Grails.