We use Docker for validation mechanisms and have built Docker images for our applications.

For container orchestration, we haven't used Kubernetes instances extensively. Docker works well for us.

It's flexible and easy to use. My team also finds it comfortable to work with.

Sometimes, it can become heavy and cause performance issues.

The stability is pretty good.

We use horizontal scaling, and it works well. Considering its container architecture, I'd rate the scalability a nine out of ten.

There are probably around 2,000 to 3,000 end users. It is extensively used.

We have used Docker's technical support. I didn't have bad experience with the customer support.

We used Kubernetes and other packaging techniques.

Portability and accessibility were the main reasons we chose Docker.

The initial setup is mostly straightforward. We used Ansible for deployment.

The ROI is high. Traditional deployments take more time and builds can be inconsistent across different environments. Docker solves these issues.

The value is there. Docker delivers high performance, leading to increased productivity. You can achieve more in less time, and your deployment cycle time is reduced.

I would rate the solution an eight out of ten.

AI with Docker is relatively new for us. But for traditional deployments like microservices and Spring Boot applications, Docker works very well.

I definitely recommend it. The landscape is changing, and Docker is transforming the way we approach deployments.

Currently, we are creating a JAR file and using microservices. There are around 178 services in a single project. We use Docker to manage and do load balancing for all the services together.

We are using Docker to host applications. We are using Docker Compose and sometimes Docker Screen.

We are facing multiple issues with the solution's stability.

We have been using Docker in the same project for five years, and we have recently deployed Docker into Kubernetes for four years.

We are facing multiple issues with the solution's stability. It is very difficult to analyze how much load a tool takes. Sometimes, our Docker images get crashed due to the unavailability of space.

I rate the solution a six or seven out of ten for stability.

Approximately, 400 users are using the solution in our organization.

I rate the solution a nine out of ten for scalability.

The solution’s initial setup is simple.

We implemented the solution through an in-house team. It took me around three to five hours to deploy the solution. Docker is easy to use and implement. For the deployment process, we used Docker in the CI/CD pipeline. Then, we pushed the Docker images to the Kubernetes as per the environment. We used Kubernetes to host and balance the load.

Since Docker is an open-source solution, it is free of cost.

Docker made it easy for us to monitor the microservices. Secondly, we were able to manage the key load balancer. Thirdly, we wanted to create a secure layer of protection for our organization. So, we started using the containers above the hypervisor.

It was like using a new operating system. We created our own network adapters. We created another isolated network inside the Docker containers to keep our organization and project safe and secure. We consider this very helpful in the secure software development life cycle.

We're implementing multiple stages in security. We are signing Docker images, Docker containers, Kubernetes containers, Kubernetes nodes, and clusters in cryptography. We are signing these so that no one tampers with the code or the docker images. We are doing this from a security point of view.

The solution's containerization helps us in providing integrity and availability. If you use a microservices architecture, I recommend implementing Docker and Kubernetes. I would recommend Docker and Kubernetes to manage multiple microservices running simultaneously.

We had to configure multiple services, like the utilization of the CPU and the utilization of the RAM for the service that we were building. Additionally, we had to mention the network adapters we will be using. We followed multiple benchmarks, like NIST Benchmarks and CIS benchmarks.

There were multiple advantages to using Docker. The most important advantage was scalability and availability. As I am working in the security team, I'm looking after the integrity of the Docker images.

Overall, I rate the solution an eight out of ten.

I use Docker for containerization, deployment, and to create packages. Docker has a wide range of uses and integrates well with other command-line tools like Terraform. Docker is most helpful when trying to work with CI/CD pipelines.

Docker's containerization property is its main selling point.

I'd like to see the new update on containers and what you can achieve with the new version of Docker by using containers. I would also like to know the range of applications for which it can be used. I want to see if new architectures have been incorporated in Docker or if we have to wait for another release.

I have been using Docker for one year.

I rate Docker a nine out of ten for stability.

Docker is a very scalable solution. I rate Docker a nine out of ten for scalability.

Docker's initial setup is straightforward. As a command line tool, it also provides you with docks to reference if you get stuck or have issues.

The solution's deployment time depends on your internet latency or internet speed and the size of the container. If you are deploying a very large application, it will take some time to set up.

Docker is deployed on-cloud in our organization.

To effectively use Docker, users should learn the basics of Docker and understand what containers and images are in Docker.

Overall, I rate Docker a nine out of ten.

We set it up a lot of times to create environments for our students.

When we teach our students, it's really important that everybody is on the same version of all their dependencies. So, Docker, we can set up the images on Docker, and it sets everybody up.

So it's a much smoother process. Without Docker, without these containers, it would be a nightmare trying to get 20 to 30 students to set up their environments correctly. So this is just a really quick and easy way to use it.

Just the portability of Docker's containers and its ability to give everybody the exact same environment and experience is most valuable to me.

It could be easier to create images and save them on reports.

Just improved development workflow, just quicker, like some better user experience creating the images for the Docker containers.

We have used it every day in my current company just to set up our environment for our build processes. We create a lot of labs.

We use the latest Docker version 4.22.

It is a very stable product.

It is extremely scalable. I would rate the scalability a ten out of ten.

The initial setup was very easy. I use it on-premises as well as in the cloud. So we use it in both places.

It's free, as far as I know.

Docker is very reliable. It's easy to scale, and it's very stable.

Overall, I would rate the solution a nine out of ten.

We work with containers for forecasting.

The solution's most valuable feature is the Dockerfile, which makes the life of developers easy. Developers get a real understanding of container creation.

I have encountered network issues while connecting with microservices. I want to optimize the application layers over the bucket. It should also have better documentation.

I have been working with the solution for seven years.

I rate the tool's scalability a nine out of ten.

We solve issues using the documentation.

Docker's implementation is straightforward. However, it can get a bit complicated when you are doing sophisticated implementation.

We have seen ROI with the tool's use.

Docker's price is good.

I rate the product an eight out of ten.

I use the tool for SQL, MySQL, and web development.

I think that with Docker, it is easy to deploy it on different platforms.

Stability is an area with a shortcoming. Hence, stability needs to be improved.

I have been using Docker for a year. Also, I don't remember the version of the solution I am using since it comes from the repository of Linux.

I rate the stability of the solution a nine out of ten.

Normally, I use it on small sites, so I don't know if it can experience scalability.

More than 200 of my students use the tool. Also, the tool is used extensively by me.

Normally, Docker is free for everything, so I don't know if there needs to be a plan to increase the number of users.

Before Docker, I used only a Linux setup.

I have used Docker on Linux for the filesystem.

The deployment of the product was done in a minute or two, considering my internet is very stable.

I use the Docker control plane for the deployment.

I was involved in the deployment process of the solution.

Docker is a free tool.

I would definitely recommend the solution to those planning to use it.

I don't know what to say to those planning to use Docker, but you can find its details on the internet.

I rate the overall solution a nine out of ten.

Docker allows you to run multiple virtual machines independently.

The solution is not easy to manage and it is one of the reasons why people introduce orchestration tools to manage it.

I have been using the solution for six to seven years.

The tool's stability is high and I would rate it a ten out of ten.

We use the solution 24/7.

The tool is an open-source product and there is no technical support for it.

We use Hyper-V and VMware as per our client's requirements.

The tool's setup is difficult and I would rate it a two out of ten. The tool's POC can be completed in a couple of hours. However, if the project is big, then deployment can take around one to two months to complete.

The solution is an open-source technology and not a commercial product. However, you will have to pay sometimes. The tool's pricing depends on the vendor.

I would rate the product a nine out of ten. The solution is a virtualization technology that is more like a mini-computer.

I think the best feature is to replicate anything in our local machine using a simple command.

The product does not have an extensive documentation. The tool does not have good scenarios. We have to go through the GitHub repository and investigate similar scenarios. Also, if you are copying multiple things, then you can jeopardize the copy number. The copying aspect also lacks a UI part. We also need to limit the memory.

I have been using the tool for four years.

The solution is stable.

The tool is very easy to scale up. My company has 100 percent usage for the product.

I have never contacted the support. I always look at GitHub instead of raising a ticket.

The product's setup is easy and straightforward. However, you will encounter difficulty in customization. The speed of the product's setup depends on the bandwidth and download speed.

The product is a free open-source tool.

I would rate the product a nine out of ten.