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 good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
Read full review Pros Packaging of application to limit the space occupied Ease of running the application Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc Read full review Ability to create branches off current releases to modify code that can be tested in a separate environment. Each developer had their own local copy of branches so it minimizes mistakes being made. Has a user-friendly UI called Git Gui that users can use if they do not like using the command line. Conflicts are displayed nicely so that developers can resolve with ease. Read full review Cons Docker hub image retention policy can be relaxed Docker hub policies can be more developer friendly Docker CLI help section can be improved Image and container storage (local) management can be optimized Read full review There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master. Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this. Many different GUIs, many people (including myself) opt to just use the command-line. Read full review Likelihood to Renew 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 Very easy to use, great tutorials, documentation and cheat sheets out there to help you become a Docker Wiz
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 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 Support Rating 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.
Nate Dillon Front-End Web Developer, Office of Mediated Education
Read full review Implementation Rating It's easy to set up and get going.
Read full review Alternatives Considered 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.
Read full review 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 a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
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 Return on Investment Reduces the number of virtual machine which impacted our quarterly billing Using docker with proxy we run multiple application on same port on same host. impact on billing is we have to provide docker training to the people who are working on it. 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