Tomcat is an open-source web server supported by Apache.
N/A
Octopus Deploy
Score 10.0 out of 10
Mid-Size Companies (51-1,000 employees)
Australian company Octopus Deploy offers their eponymous automated deployment and release management software that integrates with the user's preferred CI server and adds deployment & ops automation capabilities. Octopus Deploy enables developers, release managers, and operations folks to bring all automation into a single place. The vendor states that by reusing configuration variables, environment definition, API keys, connection strings, permissions, service principals, and automation logic,…
$12
Pricing
Apache Tomcat
Octopus Deploy
Editions & Modules
No answers on this topic
Cloud
Free 30 day trial
unlimited targets/users/projects
Server
Free 30 day trial
unlimited targets/users/projects
Enterprise
Starting at $18 per month
Enterprise
Starting at $18 per month
Server
Starting at $12 per month
Cloud
Starting at $12 per month
Offerings
Pricing Offerings
Apache Tomcat
Octopus Deploy
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Octopus Server edition is available as a 30 day free trial on our unlimited tier for any scenario, including production, and commercial use. After the trial period ends you can keep your working configuration and upgrade to a paid license and continue deploying uninterrupted.
Octopus Cloud is an alternative that is hosted by us, and is also available as a 30 day unlimited trial. No credit card is needed to create a Octopus Cloud trial instance. You can convert the Cloud trial to a paid instance at any time during or after the trial period, and keep all of your instance configuration.
Octopus also offers an Enterprise tier which offers advanced features for teams at scale including, advanced high availability, insights & DORA metrics, ServiceNow & Jira Service Management integration, unlimited instances, 24/7 support & service credits, and a Customer Success Manager.
Volume discounts are available above 500 targets, and temporary bursting for certain scenarios is supported.
More Pricing Information
Community Pulse
Apache Tomcat
Octopus Deploy
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.
We also use Ansible, which is much broader and platform/tool diverse. Octopus [Deploy] currently serves a niche for us - .Net and .Net Core deployments. It is capable of doing other things, but it does its original function better than broader tools like Ansible.
I used TFS back when it was called that, and that was a mess. ADO isn't as bad but has many limitations and things that are hard to do. The main difference is I ENJOY working in Octopus Deploy. Not so much with ADO. I'm always trying to figure out things that are stupid. …
Octopus showed better cost numbers than Azure DevOps and more flexibility against GitLab CI/CD. Octopus customization in step templates that can be reused and easily created gives big advantages against many of its competitors. Octopus was selected for these features and …
Octopus Deploy was the obvious choice at the time, its strong .net support, robustness, ease of use, and integration into an existing process was a big plus. Also, Octopus Deploy was kind enough to give my organization a not for profit community licence. In addition, the …
This software, unlike Chef, is much easier to configure or manage, since its platform provides documentation or tutorials on how to use it, besides its interface is much more modern and easy to use, it allows you to choose where you want carry out the implementations of the …
I am not aware of other products like Octopus that are available, but it is a great product for our company. We can stay ahead of the game by allowing developers to deploy code in a continuous deployment model while still maintaining the overrall infrastructure and enabling …
TeamCity is focused more on the build process. It's deployment capabilities are weak compared to Octopus. Bamboo is a proper competitor, but it is far more costly for our needs. The free version of Octopus has proven incredibly competent and sufficient for our needs, and …
There aren't really any competitors in the land of ASP.NET. Deployment is too ad-hoc. Other tools exist that have massive downsides, like Web Deploy. Most aren't even supported anymore. You could argue that containers (Docker) are a competitor, but containers cannot be used for …
Octopus Deploy is a deployment focused tool. Its purpose is to manage deployment environments. Tools like TeamCity and Visual Studio Team Services are Continuous Integration tools. You can accomplish many of the same tasks in TeamCity and VSTS but their focus on CI also means …
We looked at IBM UrbanCode Deploy and Release and Microsoft VSTS while looking for Application Release Automation tools. While VSTS doesn't work with cross-platform technologies IBM UrbanCode Deploy commands a premium price for the features it offers. Also, it needs UrbanCode …
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.
The ability to manage different stages and define a workflow is very useful for ops troubleshooting as well as deployment. You can see which version each environment has for each project, and promote or redeploy versions.
You can view deployment logs and dig deep into problems or long deployment steps.
Finding old releases can be a pain, and there isn't a good way to compare releases.
It does not really lend itself well to viewing what the content of a release is further than the version number. Ideally, you would be able to tie a deployment to the builds from the build server as well as specific commits from source control.
Many different platforms, languages, and operating systems are supported. You can deploy to your own server or the cloud. You can deploy to Windows, Linux, etc.
Many different "step templates" are included, which make it very easy to deploy what you want, how you want. Such as deploying over SSH, FTP, etc.
Support is very responsive and personable. You won't just be talking to a robot or a script. They will either solve your problem or understand it enough to solve it in a future release.
Their documentation is well thought-out and very helpful. I have found very few missing pieces.
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
Support for non-Microsoft applications needs to be improved to bring it on par with other comparable automation tools.
It doesn't yet provide integration options with other IT management tools like JIRA and HP Support to implement continuous delivery and true DevOps processes.
Support for AWS/Azure has been included very recently and it's not still very mature and feature rich and is expected to improve further in upcoming releases.
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.
Some functionality feels slightly hidden in the menu system. For example: script modules are in the same menu as packages, where I feel that are not related entities. One is code for the deployment, the other is the thing that you are deploying...
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.
Octopus Deploy is a software that runs very effectively, is easy to use, does not require such a high learning curve, provides the necessary tools to carry out the functions it offers, making it a very flexible software, it also allows that can be configured according to the needs of the user and provides integrations with other very advantageous tools since they are carried out in a very favorable way.
Octopus Deploy support has always been there for us, even when using the free tier, we get responsive hands-on help. We haven't needed to use that level of support since the documentation is clearly written, and help is readily available within the interface itself. Using Octopus Deploy is a truly joyful experience.
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.
Octopus Deploy was the obvious choice at the time, its strong .net support, robustness, ease of use, and integration into an existing process was a big plus. Also, Octopus Deploy was kind enough to give my organization a not for profit community licence. In addition, the product comes from a local Brisbane based company and it is always good to support local businesses when you can.
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.
Any automated deployment process will save your company a ton of money on testing and bugs. When you don't automate your deployments, you can't be certain that what you are moving between environments is the exact same code with the same or appropriate configuration. What you tested might not be what got deployed.
We've saved a lot of money using Octopus over the mostly manual process we were using before. We've removed a lot of the errors that come from manual, human intervention.
Octopus has also allowed us to accomplish more with fewer people. It is easy to bring new people up to speed on the deployment process, and we can be confident of success after very little training.