Apache HTTP Server vs. Mirantis Kubernetes Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache HTTP Server
Score 8.2 out of 10
N/A
Apache Web Server (Apache HTTP Server) is an open source HTTP web server for modern operating systems including UNIX and Windows.N/A
Mirantis Kubernetes Engine
Score 9.4 out of 10
N/A
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
$500
per year per node
Pricing
Apache HTTP ServerMirantis Kubernetes Engine
Editions & Modules
No answers on this topic
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
Apache HTTP ServerMirantis Kubernetes Engine
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details—These pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
More Pricing Information
Community Pulse
Apache HTTP ServerMirantis Kubernetes Engine
Considered Both Products
Apache HTTP Server
Chose Apache HTTP Server
Apache is often used in conjunction with Nginx, with Nginx in front of Apache to serve static assets like CSS and JS. Both are easy to configure. IIS is pretty cumbersome and is not as flexible as Apache.
Mirantis Kubernetes Engine

No answer on this topic

Top Pros
Top Cons
Best Alternatives
Apache HTTP ServerMirantis Kubernetes Engine
Small Businesses
NGINX
NGINX
Score 9.1 out of 10
Portainer
Portainer
Score 9.4 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache HTTP ServerMirantis Kubernetes Engine
Likelihood to Recommend
8.0
(20 ratings)
8.3
(37 ratings)
Likelihood to Renew
-
(0 ratings)
9.1
(1 ratings)
Usability
-
(0 ratings)
8.0
(2 ratings)
Support Rating
9.3
(2 ratings)
7.8
(3 ratings)
User Testimonials
Apache HTTP ServerMirantis Kubernetes Engine
Likelihood to Recommend
Apache
As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative.
On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.
Read full review
Mirantis
[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs
and separates any single application from the dependencies. Also, this tool is
helping me in the agile development of the processes. It is strongly recommended to
almost all major organizations.
Read full review
Pros
Apache
  • Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special
  • Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.
  • Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.
Read full review
Mirantis
  • Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
  • Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
  • CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.
Read full review
Cons
Apache
  • The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.
  • Security options and advanced configurations are not easy to set up and require an additional level of expertise.
  • Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.
Read full review
Mirantis
  • Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
  • Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
  • Networking is complexified due to internal port mapping between containers, etc.
Read full review
Usability
Apache
No answers on this topic
Mirantis
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
Read full review
Support Rating
Apache
I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.
Read full review
Mirantis
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
Read full review
Alternatives Considered
Apache
I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise Apache it is.
Read full review
Mirantis
We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.
Read full review
Return on Investment
Apache
  • Works as intended, so it's less to worry about.
  • Works great on elastic environments (like EC2).
  • As an Open Source project, you can get support for almost any problem you can have.
  • Configuration files, while powerful, can be tricky to dominate for some.
Read full review
Mirantis
  • Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
  • Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
  • Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.
Read full review
ScreenShots