Tomcat is an open-source web server supported by Apache.
N/A
IBM WebSphere Hybrid Edition
Score 6.8 out of 10
N/A
WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
$88.50
per month
Pricing
Apache Tomcat
IBM WebSphere Hybrid Edition
Editions & Modules
No answers on this topic
Application Server
$88.50
per month
Offerings
Pricing Offerings
Apache Tomcat
IBM WebSphere Hybrid Edition
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Tomcat
IBM WebSphere Hybrid Edition
Considered Both Products
Apache Tomcat
Verified User
Anonymous
Chose Apache Tomcat
Tomcat's configuration is simpler because it's a plaintext file that anyone can read -- and a script can manage. It's easier to monitor via Grafana. And it integrates well with software load-balancers.
Apache Tomcat is very smooth tool compared to other applications. Since there are very less feature it's very smooth. NGINX server doesn't need Apache Tomcat we can directly deploy so it faster comparatively. In my working time I have never come across the UI of NGINX. Apache …
We work with Java, and we needed to integrate Tibco RV which had a Java library. Node was not so easy to manage in the backend and we opted for something more known. As said we still love Tomcat and we heard a lot of bad experiences with NodeJS, quite tricky and slow to learn. …
Commercial application servers are available that support enterprise application needs, but many times this is overkill for most web applications running in the cloud, particularly for independent software vendors. The capabilities and management tools provided with these …
Apache Tomcat is lightweight but performs well, even when running multiple applications. Its performance and security features are the reasons for choosing Apache Tomcat among its competitors. Also, there is a huge community support than other products.
Apache Tomcat is used for our cloud-based apps when testing on our local machines. Oracle WebLogic is used for our older on-prem apps. Thus, it's difficult to compare them apples-to-apples. However, Apache Tomcat is not really meant to run in production for our older apps …
We considered between Tomcat and WebLogic and then choose Tomcat as it is much simpler and have all the features we need, also we need to integrate Tomcat with our Gitlab pipeline and Tomcat is well supported with its API set. In the future we plan to move our system to Azure …
Apache Tomcat is more lightweight and much quicker to deploy, so compared to JBoss or Weblogic it's much more efficient and cost effective for deploying small apps. The instances start up almost immediately and almost no maintenance is needed from the admins. There is also no …
Tomcat stacks up against the others very well due to its adoption in the open source community, low total cost of ownership, maintenance, and ease of deployment. It's much more lightweight than Websphere or Weblogic and provides most of the features most developers would need, …
We use WebLogic as an enterprise level large application container. We have a big WebLogic cluster, hosting our core applications. We also use tomcat to build a quick POC and some light-weighted RESTful service for a cloud-native initiative, so the relationship should be …
Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it …
Tomcat is definitely easier to implement, continues to be supported and further development to enrich the existing feature set carries on. It is the industry, de facto standard. With third party vendors offering support for the industry standard, utilizing another solution is …
As I have described before, Tomcat has competition from Jetty & frameworks like Netty. Also with NodeJs, lot of web application server side development and API development is beign done using javascript & Nodejs. So there is some decline in the use of Apache Tomcat. Though it is …
Tomcat is a more lightweight container in comparison to Oracle's Glassfish server. Glassfish however, became an enterprise product and can offer better after sales service.
Apache Tomcat is a much wider open standard than Microsoft IIS. It also seems to use fewer resources and is simpler to maintain. Troubleshooting when an issue arises is difficult. We had trouble managing the Tail logs when something strange happened. Logging is very complex and …
Well WebLogic is very complex. Most of what happens with WebLogic requires servers to be restarted, which isn't always possible. Also, Oracle tries to force you to only use their GUI interface for most of the administration, which could be done directly in the files, but are …
Relative to other solutions that worked with the Spring framework, Tomcat was the best. It worked exactly as desired and made releasing production builds a very smooth process. However, if I were able to choose, I would use one of the newer scripting languages that has a server …
GlassFish seemed to be fairly comparable in terms of easy of configuration and deployment, but we didn't do any side-by-side performance comparisons. Tomcat was better-known by the team, has more online forum support, and met the requirements of our project. Tomcat is fairly …
It's clear that JBoss is a full JEE stack implementation while Tomcat isn't, but if you don't need the whole JEE stack there are many lightweight alternatives that implement the required feature with Tomcat.
Plesk provides assistance via its community forums, knowledge base, and premium support plans. Additionally, I had trouble integrating a new website onto the hosting, which was a bit of a frantic operation because it uses more server resources than other control panels. The …
IBM Websphere was better suited for our needs as we are a primarily Java shop, and it provided better customization and potential ROI. It also requires less downtime, and support is easier than Weblogic. Also, Websphere is better suited for a hybrid environment.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its …
IBM and weblogic are equally robust and support JVM's very well but where IBM is better is its out of the box integration with active directory that makes it easier to manage access control and security posture. In addition, the licensing model for IBM is lot more flexible for …
I like the well built hybrid edition that is very favourable for our cloud apps and real-time monitoring of our applications deployment and development. I like it support real-time visibility a complete and clear view of our applications development and application awareness. I …
Both Apache Tomcat and Hybris have been in use, and we have provided support for both tomcat and IIS-based systems. Companies with a substantial investment in IBM technology will find this application particularly useful. Support and licensing fees might be prohibitive, …
WebSphere Application Server admin console is very detailed and there are a huge number of configurations available to maintain and configure. JBoss is complex where stand vs full configuration is confusing sometimes. Modularity proved complex there, so I love WebSphere …
Websphere Application Server provides better Security, high availability, easy troubleshooting, and good 24/7 support. Websphere Application Server has an easy to use interface.
WAS is an IBM product and gels with IBM database product. So, we have decided to go with IBM WAS. WAS supports more data sources than Oracle web logic. So, ideally it can be used with multiple databases.
IBM support is better than Oracle, from past experience. Weblogic and WebSphere Application Server are somewhat similar versus the open source JBOSS. For many applications we had selected WAS to have a supported platform and used some of the competitors in other various use …
I have worked on JBOSS and WEBLOGIC Application servers apart from Websphere application servers. WebSphere Application Server has a more user friendly admin console GUI. I believe WAS administration and maintenance activities are more easy and effective as compared to other …
Websphere Application Server supports enterprise Java open standards, streamlines deployment, has very flexible management capabilities and better reliability and availability.
I did not choose IBM WAS, it was a coporate decision. We are glad that we have been using this for a number of years and are quite happy as a corporation. However, it does take more time to learn WAS because of its complexity in terms of installation, various features and …
Tomcat is more than enough to deploy most of the mid-end web applications without any problem but for the high-end applications which require high scalability and high availability, which might need some tune-ups with the support of expertise in this regard. Otherwise, you may realize numerous performance issues, memory leaks, server crashes etc.
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
It works out of the box. Its basic functionality is all there and everything works with no adjustments.
The functionality is there for fine tuning, to allow applications to be easier to access and quicker with some tweaks, but again, these aren't necessary for basic running.
tomcat is just part of the J2EE specification implementation, majorly focusing on the servlet (front-end) part. If you requires the full J2ee stack, like EJB support, you need consider other containers like Weblogic
tomcat's cluster level support is very limited
tomcat's admin/configuration is not so intuitive, and default logging needs a lot of improvement
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.
Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
Commercial application servers are available that support enterprise application needs, but many times this is overkill for most web applications running in the cloud, particularly for independent software vendors. The capabilities and management tools provided with these applications are superior to Tomcat, but most times unnecessary for the vast majority of web applications developed in Java.
I did not choose IBM WAS, it was a coporate decision. We are glad that we have been using this for a number of years and are quite happy as a corporation. However, it does take more time to learn WAS because of its complexity in terms of installation, various features and special deployment and packaging needs.
It has simplified administration efforts, thus saving much time to focus on other projects and issues.
It saves us in costs, as there are no licensing requirements.
It gives us the ability to manage all of our java applets in one place, so as to be able to host both development and production systems on one server.