Docker vs. Git

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Docker
Score 8.8 out of 10
N/A
Docker Enterprise was sold to Mirantis in 2019; that product is now sold as Mirantis Kubernetes Engine. But Docker now offers a 2-product suite that includes Docker Desktop, which they present as a fast way to containerize applications on a desktop; and, Docker Hub, a service for finding and sharing container images with a team and the Docker community, a repository of container images with an array of…
$0
unlimited public repositories
Git
Score 10.0 out of 10
N/A
N/AN/A
Pricing
DockerGit
Editions & Modules
Free
$0
unlimited public repositories
Pro
$5.00
per month per user
Team
$7.00
per month per user
Business
$21
per month per user
No answers on this topic
Offerings
Pricing Offerings
DockerGit
Free Trial
NoNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
DockerGit
Considered Both Products
Docker
Chose Docker
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we …
Chose Docker
Our team uses Lando which is built on top of Docker. This makes using Docker even easier.
Chose Docker
It is easy to use. we can manage multiple images in docker hub. Docker desktop is for accessing images in our desktop. It is very much user friendly as compare to podman.
Chose Docker
Docker is by far the industry leader and mainstay when it comes to virtual machines, its really hard to justify using another service like Vagrant. The upcoming monetization of Docker desktop should make things interesting though.
Chose Docker
The features and capabilities provided by Docker are incomparable and much vast in nature. Docker is much light weight and easy to onboard into the tech stack. It is also well supported by Container orchestration systems like Kubernetes which will be critical when applications …
Chose Docker
Did use containerd or LXC for brief evaluation in the past, but settled on Docker and only see Docker as the mainstay for most organizations I worked in, as the container tool of choice so far. Docker is matured, feature-rich, and reliable enough to be the main choice all …
Chose Docker
The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.
Chose Docker
Podman has been used within our Red Hat environment, and although it supports deployments outside of RHEL, it's not as easy as Docker.
Chose Docker
Docker provides is effective container management and orchestration platform. It is highly suitable for Linux environments and allows the easy and quick deployment of production applications Other alternatives use replication and management of the virtual machines. Docker …
Git
Chose Git
We migrated from svn to Git and the transition was smooth. We have tools that migrate the complete history along with the authors of the various files and the history from svn to Git. The migration was seamless and easy. We can see complete history of check-in as if we were …
Chose Git
We were using the TortoiseSVN previously and it was super slow when we created a new branch or switched between branches. Git makes our life easy. :)
Chose Git
Git is far superior at merging than SVN and I think every other VCS from what I've heard. It's also by far the most common so using it is a no brainer. Since it's written by the one true king Linus himself there can be no question to its design and architecture.
Chose Git
The only other VCS tool I've used in production is SVN. In my option Git is a better option for several reasons. Reason one is simplicity, actions like reviewing changes, committing or stashing changes, and managing multiple feature branches is much easier with Git. The second …
Chose Git
The two main alternatives to Git that I know about are Mercurial and Subversion. I've never used either one, but I know a bit about Subversion. From what I remember, Subversion requires a server. I don't anyone using any other source control other than Git, it seems to have …
Chose Git
Git is more advanced and easier to use. It has a very simple UI and a very efficient command-line tool. Git gives you flexibility and performance for the price, and has greatly increased the complexity of workflow. The overall performance is good. It caches information locally …
Chose Git
What I know is Perforce and CVS, such other repos tend to store deltas while Git stores the snapshots of the stuff as their commit ID's. This is what makes Git much much faster when you are developing on huge repos, since the checkouts are just instantaneous.
Chose Git
Gitlab provides similar features like Git. Git is more robust, secure and developer-friendly to work on.
Chose Git
There are not many surviving alternatives for Git (maybe SVN) which in itself is quite meaningful. Git is the best versioning system of all time for programming, period. The difference between a good mathematical tool and sending .zip-s around emailing lists or FTP drives is so …
Chose Git
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria.
GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way.
G…
Chose Git
It's easy to use and stable. These are the two strengths I see in Git. It does not need a lot of time to learn, but you still need to learn it. It has high stability. Bugs are not often to see in Git, and the community support is wonderful. With the help of GitHub, you can …
Chose Git
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is …
Chose Git
I do not have much experience with other version control tools. Git is highly used everywhere and it is hard to find a development team that isn't using it. One thing I know is that with Git each developer has their own copy of a repository so they could technically work …
Chose Git
Git is the best Source Control Management Tool I've used. Every company, team, and project I've worked on professionally either used Git 100%, or was moving to Git, away from the alternatives like SVN. Git has all the features necessary, as well as a very large community of …
Chose Git
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
Chose Git
Primarily we chose Mercurial, but our customers from abroad choose Git and recommended us to use it within a project that we are doing with them. Git for us is very easy way to contribute to these projects. But from the other side we see that more and more projects and …
Chose Git
For us, we use both Git and GitHub so they were a package. I suppose you could use Git with another VCS/hosting service to track changes if it fit well enough, but for us we just went with design out of the box. We pay for the GitHub private repository for the extra security.
Chose Git
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in …
Chose Git
N/A. No other products like Git were used.
Chose Git
Branching and merging are easy: Branching is a walk in the park. It feels like a natural part of the workflow. They are cheap (fast and consume very little space) so that you can branch whenever you want. This means you can sandbox your features and ideas till they are ready …
Chose Git
Git is pretty much the main choice today when choosing a source control system. There are still others out there like Subversion and Mercurial, however I have not evaluated these as they are older than Git and I tend to try to stay on the leading edge of what is in use for the …
Chose Git
Git is a distributed version control system. There is more flexibility to work with a bigger team. You can modify the same file and later merge all changes into a single file.
Chose Git
After using Subversion previously for a number of years, Git comes across as the new and improved source control approach. Git seems very suited to working with Agile:- branches can be created easily, allowing multiple developers to switch to them quickly, and having local …
Chose Git
While my experience is limited on Microsoft Team Foundation Server, my understanding is that it works only for windows development work. This leaves out developers of alternative languages. Since git allows any code to be placed in it (you could even use it to back up plain …
Best Alternatives
DockerGit
Small Businesses
Git
Git
Score 10.0 out of 10
GitHub
GitHub
Score 9.2 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitHub
GitHub
Score 9.2 out of 10
Enterprises
Git
Git
Score 10.0 out of 10
Perforce P4
Perforce P4
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
DockerGit
Likelihood to Recommend
10.0
(0 ratings)
10.0
(0 ratings)
Likelihood to Renew
9.1
(0 ratings)
10.0
(0 ratings)
Usability
10.0
(0 ratings)
9.0
(0 ratings)
Availability
10.0
(0 ratings)
-
(0 ratings)
Performance
8.0
(0 ratings)
-
(0 ratings)
Support Rating
-
(0 ratings)
8.5
(0 ratings)
Implementation Rating
-
(0 ratings)
9.0
(0 ratings)
Product Scalability
10.0
(0 ratings)
-
(0 ratings)
User Testimonials
DockerGit
Likelihood to Recommend
You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
Read full review
Git is by far the best Source Control Management Tool I've used. I would recommend it to anyone, whether it's an individual working on their own project, a small start-up company, or a huge organization with thousands of developers. Maintaining code via source control is absolutely mandatory for all developers everywhere.
Read full review
Pros
  • Kubernetes context switching - very handy
  • Integrate well and seamless - No complicated setup and or UX
  • Ease of updating images and etc - very important
Read full review
  • Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
  • Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
  • Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
Read full review
Cons
  • It will be nice to see an admin UI for configuration of images
  • Container networking can be simplified
  • Data storage/volume management can be simplified
Read full review
  • Some of the commands are a little obtuse if you're not using a Git Client
  • Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
  • It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
Read full review
Likelihood to Renew
No answers on this topic
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Read full review
Usability
I have been using Docker for more than 3 years and it really simplifies the modern application development and deployment. I like the ability of Docker to improve efficiency, portability and scalability for developers and operations teams. Another reason for giving this rating is because Docker integrates CI/CD pipelines very well
Read full review
Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review
Reliability and Availability
Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.
Read full review
No answers on this topic
Performance
Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.
Read full review
No answers on this topic
Support Rating
No answers on this topic
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Read full review
Implementation Rating
No answers on this topic
It's easy to set up and get going.
Read full review
Alternatives Considered
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we defined a docker file which will be our base image and we performed all our activities inside that image to build infrastructure using terraform. Integration we have done in our gitlab pipeline and finally we remove the docker image so that the space can be reclaimed immediately.
Read full review
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. GIT have the facility to quickly fetch the complete repository on to your local system.
Read full review
Scalability
It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.
Read full review
No answers on this topic
Return on Investment
  • With Docker adoption, were able to reduce 40% of the time taken to complete workspace setup
  • Provided the environment packaging / configurability capability which enabled resource sharing and interoperability across teams
  • Were able to leverage off the shelf images provided by leading product companies which increased reliability and security exponently
Read full review
  • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
  • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
  • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Read full review
ScreenShots