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.
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.
Student at Prince of Songkla University (Sritrang'NET)
Real User
Top 10
2023-07-04T07:32:00Z
Jul 4, 2023
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 is considered to be a flagship product when it comes to containerization. If a person is going to run containers for developers, Docker should probably be chosen. Docker's enterprise version is also a great solution. For any enterprise organization that is running containers or building or developing application containers, Docker will offer some great features that allow a person to collaborate with the whole development team and manage everything. Docker provides its users with the functionality to control and manage everything. Since Docker is the best solution in terms of containerization, I rate the overall solution a ten out of ten.
I'm not sure which version of the solution we're using. It's likely the latest. I'd recommend the solution to others. It is very easy to use. I'd rate it eight out of ten.
I would rate this solution as seven out of ten. My advice is to create an account on Docker Hub. In Docker Hub, there are three Docker images available for practice. We use GitHub to see how we're making the Docker images and then push it to the public Docker Hub. I have an account in Docker Hub and have images there that I can reuse later. I would also advise completing a Udemy course for Docker or watching YouTube videos about it. This will make Docker easier to understand.
Documentation is quite good. In addition, if I am testing for errors, then community support also goes to any kind of zero-out solution. Most of the data solutions available in the community are in the Docker workflow. I would rate the Docker solution a seven out of ten, with one being the worst and 10 being the best in the field.
I rate Docker 8.5 out of 10. From a business perspective, Docker is the de facto standard, and it's going to cost you less to use it than to try to find an alternative unless there's something that Docker can't do. It's going to cost you less because there are so many more free resources available. Your team can Google and find technical information much more easily about Docker than any other solution. The advice I'd give to someone who is new to the solution is to find an online course that can walk you through Docker because it can be really confusing to get up to speed on it.
Tech Lead Consultant | Manager Data Engineering at Ekimetrics
Real User
Top 5
2022-11-07T12:29:47Z
Nov 7, 2022
I rate the solution a nine out of ten. I advise users considering the solution to learn how to use it as soon as possible so they can easily conduct deployments.
I would recommend they use the online videos and tutorials and after a week they are going to be ready to start. I would recommend it to anyone to use. I would rate Docker an eight out of ten.
This solution is being developed and improved regularly, so we recommend organizations to look at the cloud-based variant. This will make it easier to stay as up to date as possible. I would rate this solution an eight out of ten.
Specialist - Cloud Services and Software at NRG Energy, Inc.
Real User
Top 10
2022-09-28T15:06:17Z
Sep 28, 2022
My advice to others is they should use this solution. Previously we had to set everything up for small deployments in the environment, but with Docker, we can directly run the application in a container and pull any images. We don't need to set it up. We can use an image and we can directly set it up. I rate Docker an eight out of ten.
Unix/Linux Systems Administrator at a financial services firm with 10,001+ employees
Real User
Top 20
2022-08-19T18:57:00Z
Aug 19, 2022
The founder of Docker decided to move to Docker Enterprise to make revenue. There are many people moving away from Docker. My advice to others is if you are using legacy applications they do not run well with containers. The person wanting to use Docker has to ask themself questions about themselves to determine if this solution is best. For example, the application that they want to run has to be scalable. People think Docker or Kubernetes is going to solve their problems, but no. If you have problems, it's going to amplify them, but if you have easy, smooth applications, it's going to make your life easier. The application itself has to be scalable. The application has to be container ready, such as login inputs, does it follow the 12-Factor principles of deployment, and has security. Even if you don't have security, Docker can help with security if you don't have application security. You need to consider how you are going to patch the images or the applications and if it will work with languages on WiFi, such as Java, Python, or Ruby version. Those are requirements you need to meet before deploying Docker. You have to find answers to many questions. I rate Docker a seven out of ten. I gave my rating a seven out of ten because autoscaling is necessary for cloud-native applications and it is not available. However, it's easy to use, scalable, and straightforward. It was the defacto container runtime for a long time until they went to an enterprise. Docker is very good in CI/CD. Anybody building images is using Docker to build the images and it works well with CI/CD.
Docker takes away repetitive, mundane configuration tasks and is used throughout the development lifecycle for fast, easy and portable application development – desktop and cloud. Docker’s comprehensive end to end platform includes UIs, CLIs, APIs and security that are engineered to work together across the entire application delivery lifecycle.
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.
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.
I rate the product an eight out of ten.
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.
I would rate the product a nine out of ten.
Docker is considered to be a flagship product when it comes to containerization. If a person is going to run containers for developers, Docker should probably be chosen. Docker's enterprise version is also a great solution. For any enterprise organization that is running containers or building or developing application containers, Docker will offer some great features that allow a person to collaborate with the whole development team and manage everything. Docker provides its users with the functionality to control and manage everything. Since Docker is the best solution in terms of containerization, I rate the overall solution a ten out of ten.
I'm not sure which version of the solution we're using. It's likely the latest. I'd recommend the solution to others. It is very easy to use. I'd rate it eight out of ten.
This solution is doing its job well. The stability could improve, but the other parts of the solution are great. I rate Docker an eight out of ten.
I would rate this solution as seven out of ten. My advice is to create an account on Docker Hub. In Docker Hub, there are three Docker images available for practice. We use GitHub to see how we're making the Docker images and then push it to the public Docker Hub. I have an account in Docker Hub and have images there that I can reuse later. I would also advise completing a Udemy course for Docker or watching YouTube videos about it. This will make Docker easier to understand.
Documentation is quite good. In addition, if I am testing for errors, then community support also goes to any kind of zero-out solution. Most of the data solutions available in the community are in the Docker workflow. I would rate the Docker solution a seven out of ten, with one being the worst and 10 being the best in the field.
I rate Docker 8.5 out of 10. From a business perspective, Docker is the de facto standard, and it's going to cost you less to use it than to try to find an alternative unless there's something that Docker can't do. It's going to cost you less because there are so many more free resources available. Your team can Google and find technical information much more easily about Docker than any other solution. The advice I'd give to someone who is new to the solution is to find an online course that can walk you through Docker because it can be really confusing to get up to speed on it.
I rate the solution a nine out of ten. I advise users considering the solution to learn how to use it as soon as possible so they can easily conduct deployments.
I would recommend they use the online videos and tutorials and after a week they are going to be ready to start. I would recommend it to anyone to use. I would rate Docker an eight out of ten.
This solution is being developed and improved regularly, so we recommend organizations to look at the cloud-based variant. This will make it easier to stay as up to date as possible. I would rate this solution an eight out of ten.
My advice to others is they should use this solution. Previously we had to set everything up for small deployments in the environment, but with Docker, we can directly run the application in a container and pull any images. We don't need to set it up. We can use an image and we can directly set it up. I rate Docker an eight out of ten.
The founder of Docker decided to move to Docker Enterprise to make revenue. There are many people moving away from Docker. My advice to others is if you are using legacy applications they do not run well with containers. The person wanting to use Docker has to ask themself questions about themselves to determine if this solution is best. For example, the application that they want to run has to be scalable. People think Docker or Kubernetes is going to solve their problems, but no. If you have problems, it's going to amplify them, but if you have easy, smooth applications, it's going to make your life easier. The application itself has to be scalable. The application has to be container ready, such as login inputs, does it follow the 12-Factor principles of deployment, and has security. Even if you don't have security, Docker can help with security if you don't have application security. You need to consider how you are going to patch the images or the applications and if it will work with languages on WiFi, such as Java, Python, or Ruby version. Those are requirements you need to meet before deploying Docker. You have to find answers to many questions. I rate Docker a seven out of ten. I gave my rating a seven out of ten because autoscaling is necessary for cloud-native applications and it is not available. However, it's easy to use, scalable, and straightforward. It was the defacto container runtime for a long time until they went to an enterprise. Docker is very good in CI/CD. Anybody building images is using Docker to build the images and it works well with CI/CD.