Apache Subversion vs. Git vs. Proxmox VE

It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.

Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.

Incentivized

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.

Incentivized

We used Proxmox to implement private cloud services, for clusters
of a small number of servers, from 3 to 11 with and without high
availability. Allways with ZFS file systems, and we used to install the
root pool in SSDs mirrored and use other pools with RAID 10 in groups of
four, for the virtual machines and containers, for the backups and snapshots, we used magnetic disks with RAID 10, in groups of four. Do
not use an even number of servers because does not facilitates the
implementation of High Availability, because the corosync service must
have an odd number of servers to detect a failed server for the quorum
system. We used a variety of servers, from clone PCs with AMD Ryzen with 6 cores and 12 threads with 64 GB of RAM no ECC, to high end servers with 64 cores and 128 threads per cpu and 2 cpus per server, with AMD EPYC Rome or Milan, 2 terabytes of RAM ECC.

Incentivized

• Revision control done properly - you have end to end visibility of all changes in the project.
• Conflict resolution - visually highlighting the differences helps to track down the problem.
• Being open source and very popular.
• We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
• Rollbacks are made simple and easy to use.

Incentivized

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

Incentivized

• BackUp System, provides extensive propiertes and verifications. An exclusive server for BackUp Administration (PBS)
• Hardware Customization. You can select several properties to adapt the hardware to your needs
• Easy administration. You will be able to manage the server with easily accessible tools such as the web console and usage statistics.
• Certificates Administration.

• Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
• Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
• Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.

Incentivized

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

Incentivized

• The web UI does not work as well on mobile devices. It is useable, but a mobile optimised / responsive UI would be nice to have. There is a mobile app, so that may alleviate this issue, but I have not yet tried it.
• Support in the community forums could be better. There are paid support plans, but new users trying out the software will not have access to this. Answers to questions can sometimes be terse, and I can imagine this may put some people off.
• The wiki is a bit hit and miss with certain topics. I've often seen outdated or missing information, and the whole thing looks like it could do with some polish. I'd love to see it opened up for the community to add to.

Incentivized

While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.

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.

Incentivized

Proxmox VE provides the most capable, yet stable virtualization platform in the market today. Licensing options are also competitive and cost-effective for support, and support is extremely fast and knowledgable of getting issues resolved as quickly and soundly as possible.

Incentivized

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.

Incentivized

The interface is easy to use for most of it, but still lacks screens for some configurations. Also, a few of the screens are not as intuitive as they could be. This is specially true with disk and network configuration, where some graphic/visual representations of the configurations would be very useful

Incentivized

Proxmox VE's ha-cluster functionality is very much improved, though does have a not-very-often occurrence of failure. In a 2-node cluster of Proxmox VE, HA can fail causing an instance that is supposed to migrate between the two nodes stop and fail until manually recovered through the command-line tools provided. Other than this, the HA clustering capability of Proxmox VE has proven to be reliable in 3 or more clustered environments with much less chance of these failures to occur.

Incentivized

Proxmox VE's interfacing is always fast to load, both the Web interface and the command-line tool interfaces. Reporting is practically real time almost all the time, and you can see everything in mere seconds, easily able to identify if something is wrong or it everything is in tip-top shape as always desired

Incentivized

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.

Incentivized

They are fast, understanding, very intelligent, know their product very well, fast, responsive, and concise. Need I say more?

Incentivized

It's easy to set up and get going.

Incentivized

It worked, was easy and super fast to deploy, and provided everything we needed in a matter of minutes

Incentivized

Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.

Incentivized

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.

Incentivized

Proxmox VE is cheaper than VMware, especially upscaling an HA architecture. Compared with other free or less expensive solutions, Proxmox VE is high compatible with more types of hardware solutions and more VM types. From my point of view, Proxmox VE has no competitor at the same price level, it offers the most complete and production-ready HA solution.

Incentivized

Proxmox VE provides everything you need to quickly add new storage mediums, network and local, as well as networking interfaces, such as using Linux standard bridges and now Open-vSwitch bridges which can be even more scalable than before. Proxmox VE 4.0 dropped support for OpenVZ in favor of the more well supported and native LXC and made an upgrade path to it very simple.

Incentivized

• Subversion helps us feel secure in maintaining access to all of our product code, both current and historical.
• Being free and open source makes it an even better "investment".

Incentivized

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

Incentivized

• Due to the open source nature of Proxmox, we have no licensing costs while training our employees
• We've migrated 100% of our clients to Proxmox and have found improved uptime, and flexibility.
• In the 10 years of using Proxmox, we've yet to lose any data or not be notified of backup issues.

Incentivized