Should i use tomcat or jboss

Connect and share knowledge within a single location that is structured and easy to search. I am starting to look into Enterprise Java and the book I am following mentions that it will use JBoss. Netbeans ships with Glassfish. I have used Tomcat in the past.

Tomcat is just a servlet container, i. Tomcat is very popular for simple web applications, or applications using frameworks such as Spring that do not require a full Java EE server.

Administration of a Tomcat server is arguably easier, as there are fewer moving parts. However, for applications that do require a full Java EE stack or at least more pieces that could easily be bolted-on to Tomcat JBoss has a larger and deeper user community, and a more mature codebase. Also, for those who prefer a GUI-based admin system GlassFish's admin console is extremely slick, whereas most administration in JBoss is done with a command-line and text editor.

Some things to consider:. A Servlet Container e. An Application Server e. This includes Tomcat as web container internally. This also has two flavors:. This has its own web container not Tomcat. This comes from Oracle itself, so all new specs will be tested and implemented with Glassfish first. So, always it would support the latest spec. I am not aware of its support models. The main difference between JBoss, Glassfish but also WebSphere, WebLogic and so on respect to Tomcat but also Jetty, was in the functionality that an full app server offer.

However to day with advanced Framework such as Spring and Guice, many of the main advantage of using an a full stack application server can be mitigate, and with the assumption of a one of this framework manly with Spring Ecosystem, you can benefit of many sub project that in the my work experience let me to left the use of a full stack app server in favour of lightweight app server like tomcat.

It seems a bit discouraging to use Tomcat when you read these answers. However what most fail to mention is that you can get to identical or almost identical use cases with tomcat but that requires you to add the libraries needed through Maven or whatever include system you use.

The substantial difference between the two is that JBoss provides a full Java Enterprise Edition Java EE stack, including Enterprise JavaBeans and many other technologies that are useful for developers working on enterprise Java applications.

Tomcat is much more limited. One way to think of it is that JBoss is a Java EE stack that includes a servlet container and web server, whereas Tomcat, for the most part, is a servlet container and web server. Apache tomcat is just an only serverlet container it does not support for Enterprise Java application JEE. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. What determines an effective ecommerce KPI? As a business operator, you may be wondering what ecommerce KPIs are most important for your company.

This comprehensive guide provides you with all you need to know about ecommerce KPIs and metrics. Would you like to learn more about the fastest and easiest way to fulfill your ecommerce orders? Read our complete review of Deliverr to discover how you can rapidly grow your ecommerce business with the fastest fulfillment delivery service on the market today.

Business blogging is a free marketing tool that can help you attract new customers and create relationships with them. Reseller Hosting. Ruby on Rails Hosting. ColdFusion Hosting. NET Hosting. Home » Blog. Which Server is Right for You?

Editorial Team. We are the Editorial Team at DailyRazor, and we're passionate about bringing you the latest content on web design, web hosting, business, and technology-related topics. We work hard to ensure that our articles are well-written with a high level of quality for your reading pleasure!

Leave a Reply Cancel reply Your email address will not be published. Get The Latest Updates. The application server can be considered as a superset of a Web Server. Another point of consideration is that most application servers have Web Servers as an integral part of them.

Though most Web Servers now have plugins like, they were primarily designed to serve static content. Web Servers are primarily file-centric and application servers are application-centric.

And application servers bring in things like Application - Management, Packaging, Deployment, and Runtime services. With regard to resource utilization, Application Servers tend to be heavier than web servers. The concept of multi-threading is alien to web servers. Application Servers not only use multi-threading but also connection pooling, isolation pooling, and transaction features.

Now that you have got an idea about what an application server is and how it is different from a web server, let us look at the two of the most popular application servers: JBoss and Tomcat.

It serves enterprise customers looking for pre-configured profiles of JBoss Enterprise Middleware components that have been tested and also certified providing an integrated experience. It is not only ideal for users who have just started with J2EE but also for senior architects requiring a more customizable middleware platform. JBoss has popularity because the usage is simple and easy.

It is also very easy to debug since the source code is readily available and also creating customized versions for personal or business use is very easy. The Enterprise-class reliability, scalability, high availability, and performance are some of its features. It is a safe choice for portable applications and the service-oriented architecture provides consistency making it embeddable. The interaction with middleware services is further simplified due to its aspect-oriented architecture.

This would mean JRE is sufficient in production environments. Having said that, it is recommended to have that extra set of JDK tools on the system. Apache Tomcat is a widely used application due to its lightweight, effective, and efficient nature. It is the result of an open collaboration between developers. The Apache web site has made both the binary and source versions available.

Tomcat can be used as either a standalone product with its own internal Web server or together with other Web servers. Since the performance of Tomcat as a web server can't be compared to that of a designated one, people go for the likes of Apache HTTP Server. Tomcat is a web server and a web container in one. We can't compare Tomcat and JBoss, because one of them is a superset of the other.

JBoss is Tomcat plus JMS messaging provider, Web Services engine, Management capabilities, scripted administration interface, data grid solution, Advanced security, dynamic and powerful clustering engine, and Transaction management service. Saying JBoss is better than Tomcat or the other way around would be very erroneous. Factors like situation, architecture come into play.

JBoss is very powerful, but it is more complicated than Tomcat and also consumes considerably more memory and processing resources.