Mirantis Kubernetes Engine Reviews and Ratings

Use Cases and Deployment Scope

It is used in a project in our enterprise. It helps us to scale individual components independently. Only a little times we faced issues with Mirantis Cloud Native Suite (Docker Enterprise). Rest of the time I assure that it worked properly. We can also keep it on autoscale. And it works really well at peak times as well.

Likelihood to Recommend

Mirantis Cloud Native Suite (Docker Enterprise) is well suited for extracting docker images of large applications and test the application for various operating systems and all. It is well suited for business applications, customer applications etc. and not suited for financial applications because there may be security concerns so use it wisely

Use Cases and Deployment Scope

Docker Enterprise is quite a handy solution when it comes to containerizing your application making it lightweight and easy to spin and access. Currently, it is being used across the whole organization and [is a] solution for every kind of complex problem.

Likelihood to Recommend

Mirantis solution is really helpful when your critical application is containerised and if you are facing any kind of problems related to containers. You don't have to rely on the community for your issue, you can raise a ticket with the vendor and the resolution is quite fast.

It [is] quite expensive when it comes to pricing and almost all the features can be utilized using the community edition which is free.

Use Cases and Deployment Scope

Through

[Mirantis Cloud Native Suite (Docker Enterprise)] I have got rid of the improperly-signed and even unsigned container

workloads. This tool is easy to configure and easily I can tag the workloads

for execution on appropriate node types. Further through this application, it is

very convenient for me to use specialized hardware in bare metal which includes

FPGAs and GPUs, that offer great machine learning and helps in scientific

computing.

Likelihood to Recommend

[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.

Use Cases and Deployment Scope

Docker is heavily used to containerized the projects and upload it to kubernetes. It is helpful when developing microservices. Due to Dockers isolation and portability feature, it is easy to deploy run and get a microservice up in no time. Docker is being used across the whole organization. Docker address following business problems: building independent microservices, isolation and easy potability.

Likelihood to Recommend

I would definitely recommend Docker to my colleagues if they are planning to build a microservice. The containers not only saves space but also time. The ease of portability helps to pass it among the team and helps them to get the setup ready in no time. It is a great way to save some developers repetitive task.

Use Cases and Deployment Scope

We use Swarm to deploy internal applications in a managed cluster. These applications are mission-critical and used across all departments in the organization. Swarm solves the problem of scaling and load balancing traffic and resources during peak business hours. It allows fast and simple automated deployment which drastically reduces the time spent on this task by developers.

Likelihood to Recommend

Swarm is well suited to deploy in an infrastructure of distributed micro-services and orchestrating them from a central platform. It does this job very well, and if you're looking for this functionality, I highly recommend Swarm. However, if you're simply looking for a load balancing and horizontal scaling, I think there are far better and even simpler tools available more suited to that task.

Use Cases and Deployment Scope

Docker is everywhere, there just isn't a server on an application which is not present in Docker. It forms the integral part of the whole infra for us. The beauty of Docker comes from its amazing quality of being robust, easy to start and very easy to blow it off completely. It's the most powerful tool which just does magic for us.

Likelihood to Recommend

For CI/CD it is the best tool to use. If you want to manage an infra where there are millions of machines needed you need to start using Docker if you are not.

Use Cases and Deployment Scope

Docker is used by most of our teams as part of their development and deployment practice. For development, it enables engineers to build applications in the same environment without worrying about local configuration issues. Nearly all of our CI/CD and infrastructure runs in Docker containers as well, which makes debugging production issues (especially around deployment) as simple as pulling down the right image and poking at it locally.

Likelihood to Recommend

Docker is the best widely-used solution for isolated development environments and predictable deployments. However, for teams that work with only one specific technology stack, using Docker for local development can introduce more complexity. It shines when teams have to move between many different types of projects, but is "overkill" for a single application with minimal dependencies.

Use Cases and Deployment Scope

We are currently using Docker in a test environment to deploy and monitor all of our servers/firewalls/switches/etc. throughout our company. We have a single server instance that houses all the containers and images. My department, the technology services department, is the only department that uses this and as it is still only being tested only one user is using/deploying/managing it—me. But it allows me to have a glance at each location to see if there are any issues that could potentially take down a site.

Likelihood to Recommend

It would really all depend on what they are looking to do. We are planning on using it as a monitoring tool for our locations. There are tons of different ways Docker can be used so as it said, it depends on the use case. Not only do I use Docker for my company but I use it at home as well and there it is a beautiful and amazing tool for HTPC users, I just wish I had found it sooner.

Use Cases and Deployment Scope

Docker is used by our company to build our server deployment files and to run tests. This allows us to have confidence that our deployments will work correctly in our pull request tests. Developers can also be confident that the build will run the same every time no matter where the code is being run.

Likelihood to Recommend

Docker gives developers flexibility and repeatable outcomes. It is very useful for developing with confidence and knowing that all environments will behave the same. Not all developers like to use Linux for developing, so being able to run a Linux instance on Windows allows team members to develop on their OS of choice.

Use Cases and Deployment Scope

We use Docker for WordPress development. It has replaced Vagrant on our development systems. We like the tighter integration with Windows Hyper-V and the performance is better than VirtualBox-based solutions. We are able to jump-start many projects with the Docker Compose files people contribute and publish on GitHub. Using Docker Compose we are able to create reliable, consistent, development scaffolding.

Likelihood to Recommend

It's excellent when you need to run several simultaneous containers and has much better performance than Vagrant or VirtualBox based solutions. It's easier to configure than VMWare. It doesn't seem appropriate if you need GUI access inside the container, I'm not sure that's even possible. SSH access is possible, but a little cumbersome.