Apache Tomcat vs OpenShift vs Stackato

Overview

Red Hat OpenShift

Stacks1.6K

Followers1.4K

Votes517

GitHub Stars885

Forks510

Stackato

Stacks11

Followers25

Votes2

Apache Tomcat

Stacks16.9K

Followers12.6K

Votes201

GitHub Stars8.0K

Forks5.3K

Apache Tomcat vs OpenShift vs Stackato: What are the differences?

Introduction

In this comparison, we will outline the key differences between Apache Tomcat, OpenShift, and Stackato.

Deployment Environment: Apache Tomcat is an open-source server for deploying Java Servlets and JSPs, while OpenShift is a Platform as a Service (PaaS) that allows you to deploy applications in a cloud environment. Stackato, on the other hand, is a Platform as a Service (PaaS) that can run on a public or private cloud.
Scalability and Resource Management: OpenShift provides auto-scaling features, allowing your application to scale based on demand, while Apache Tomcat's scalability is dependent on manual configurations. Stackato offers built-in support for horizontal scaling and resource allocation, providing efficient resource management.
Ease of Deployment: Apache Tomcat may require manual configurations for deployment, while OpenShift streamlines the deployment process with its user-friendly interface and tools. Stackato simplifies deployment by supporting multiple programming languages and frameworks out of the box, making it easier to get your applications up and running quickly.
Monitoring and Logging: OpenShift includes built-in monitoring and logging tools to help you track the performance of your applications, while Apache Tomcat may require third-party plugins or configurations for comprehensive monitoring. Stackato offers robust monitoring and logging capabilities, enabling developers to troubleshoot and optimize their applications effectively.
Community Support and Ecosystem: Apache Tomcat has a large and active community that provides support and resources for developers, while OpenShift benefits from being part of the Red Hat ecosystem, offering enterprise-grade support and services. Stackato is backed by ActiveState, providing commercial support and a curated ecosystem of technologies for developers.
Cost and Pricing Model: Apache Tomcat is free to use, with no licensing fees, making it a cost-effective option for small-scale deployments. OpenShift offers a freemium pricing model, providing free tiers for basic usage and paid plans for additional features and resources. Stackato follows a subscription-based pricing model, offering different tiers based on usage and support needs.

In Summary, Apache Tomcat, OpenShift, and Stackato differ in their deployment environment, scalability features, ease of deployment, monitoring capabilities, community support, and pricing models.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Red Hat OpenShift, Stackato, Apache Tomcat

Hari

Mar 3, 2020

Needs advice

I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to

configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly.
Install apache and tomcat.
Generate and apply selfsigned certs to http server.
Modify default ports on Tomcat to different ports.
Create users on RHEL for application support team.
other administrative tasks like, start, stop and restart HTTP and Tomcat services.

I have utilized the power of ansible for all these tasks, which made it easy and manageable.

419k views419k

Comments

Detailed Comparison

Red Hat OpenShift	Stackato	Apache Tomcat
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.	Stackato runs on top of your cloud infrastructure, and is the middleware from which your applications are launched. Developers simply upload their application source files to Stackato via IDE or command-line. Stackato automatically configures the required language runtimes, web frameworks, and data and messaging services.	Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
Built-in support for Node.js, Ruby, Python, PHP, Perl, and Java (the standard in today's Enterprise);OpenShift is extensible with a customizable cartridge functionality that allows developers to add any other language they wish. We've seen everything from Clojure to Cobol running on OpenShift;OpenShift supports frameworks ranging from Spring, to Rails, to Play;Autoscaling- OpenShift can scale your application by adding additional instances of your application and enabling clustering. Alternatively, you can manually scale the amount of resources with which your application is deployed when needed;OpenShift by Red Hat is built on open-source technologies (Red Hat Enterprise Linux- RHEL);One Click Deployment- Deploying to the OpenShift platform is as easy a clicking a button or entering a "Git push" command	Web console; Activity timeline; Multi-tenancy; App store; LDAP support; Oracle support; Amazon RDS integration; Self-service for developers; Uses buildpack; One-click SSO for deploys apps; Log streaming; Availability zones and placement zones support; Auto-scaling of app instances; Auto-scaling at infrastructure layer; Runs on vSphere, OpenStack, CloudStack, AWS, Rackspace, KVM, Virtualbox, VMware Fusion	-
Statistics
GitHub Stars 885	GitHub Stars -	GitHub Stars 8.0K
GitHub Forks 510	GitHub Forks -	GitHub Forks 5.3K
Stacks 1.6K	Stacks 11	Stacks 16.9K
Followers 1.4K	Followers 25	Followers 12.6K
Votes 517	Votes 2	Votes 201
Pros & Cons
Pros 99 Good free plan 63 Open Source 47 Easy setup 43 Nodejs support 42 Well documented Cons 2 Decisions are made for you, limiting your options 2 License cost 1 Behind, sometimes severely, the upstreams	Pros 2 Compliance - Owning the data helps with SOX, etc	Pros 79 Easy 72 Java 49 Popular 1 Spring web Cons 3 Blocking - each http request block a thread 2 Easy to set up
Integrations
No integrations available	OpenStack Apache CloudStack Amazon EC2 Rackspace Cloud Servers VirtualBox VMware vSphere Cloud Foundry Docker	No integrations available

What are some alternatives to Red Hat OpenShift, Stackato, Apache Tomcat?

NGINX

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

Heroku

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Google App Engine

Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

AWS Elastic Beanstalk

Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Render

Render is a unified platform to build and run all your apps and websites with free SSL, a global CDN, private networks and auto deploys from Git.

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase

Apache Tomcat vs OpenShift vs Stackato: What are the differences?

Introduction

In this comparison, we will outline the key differences between Apache Tomcat, OpenShift, and Stackato.

Deployment Environment: Apache Tomcat is an open-source server for deploying Java Servlets and JSPs, while OpenShift is a Platform as a Service (PaaS) that allows you to deploy applications in a cloud environment. Stackato, on the other hand, is a Platform as a Service (PaaS) that can run on a public or private cloud.
Scalability and Resource Management: OpenShift provides auto-scaling features, allowing your application to scale based on demand, while Apache Tomcat's scalability is dependent on manual configurations. Stackato offers built-in support for horizontal scaling and resource allocation, providing efficient resource management.
Ease of Deployment: Apache Tomcat may require manual configurations for deployment, while OpenShift streamlines the deployment process with its user-friendly interface and tools. Stackato simplifies deployment by supporting multiple programming languages and frameworks out of the box, making it easier to get your applications up and running quickly.
Monitoring and Logging: OpenShift includes built-in monitoring and logging tools to help you track the performance of your applications, while Apache Tomcat may require third-party plugins or configurations for comprehensive monitoring. Stackato offers robust monitoring and logging capabilities, enabling developers to troubleshoot and optimize their applications effectively.
Community Support and Ecosystem: Apache Tomcat has a large and active community that provides support and resources for developers, while OpenShift benefits from being part of the Red Hat ecosystem, offering enterprise-grade support and services. Stackato is backed by ActiveState, providing commercial support and a curated ecosystem of technologies for developers.
Cost and Pricing Model: Apache Tomcat is free to use, with no licensing fees, making it a cost-effective option for small-scale deployments. OpenShift offers a freemium pricing model, providing free tiers for basic usage and paid plans for additional features and resources. Stackato follows a subscription-based pricing model, offering different tiers based on usage and support needs.

In Summary, Apache Tomcat, OpenShift, and Stackato differ in their deployment environment, scalability features, ease of deployment, monitoring capabilities, community support, and pricing models.