[closed] GIT or RTC source control?
Hi,
We have a large SVN repository, and we're planing to migrate it to either, GIT or RTC SCM. Do you know if there is some comparative analysis done? I would like to know which are the differences between both tools. The cost is not important, I just want to see something like a comparative chart between the features of both, GIT and RTC.
We´re currently using RTC for planning, and RQM as testing management tool, so the integration with this tools is a important point to take into account.
I will really appreciate your help.
Regards,
The question has been closed for the following reason: "The question is answered, right answer was accepted" by davidhoney Sep 21 '23, 6:56 a.m.
Accepted answer
10 other answers
Go with Git ... we are working with RTC now since nearly 8 years ... and my company has setup the "recommended hardware/network setup" with load balancers and caching-proxies for devs/buildservers/locations etc. ... RTC is a pain mainly due to its instability. (just again a huge bunch of people is idling now for 2 days, because RTC is down).
RTC server is comming up from time to time, but then extremely slow or not reachable again 5 minutes later.
(IT guys always say: "load is too heavy ... by buildservers and developers ... so >everything< collapses)
In my opinion the major flaw is the "always online" concept, which isn't bad but implied a very "network traffic" hungry underlying tool chain. (I expect nearly every second mouse-click need to be synchronized with the RTC server, what generates something like "IBM designed" DoS-attack on its own servers)
Git on the other hand is designed to work "offline", so the "network traffic" is way smaller, because you can work a long period of time without the need to download/upload/communicate with any server.
"Integration of tool-chain" is in this case even a "negative" because it means: If server is collapsing under load you can do "nothing anymore". You cannot work on code, you cannot check work items, you cannot perform reviews, you cannot do anything "but working on mails" (because mail server is MS not down).
So the "Down-Time" of RTC combined with the "high integration" (on one vendor server and tool-chain) is a real productivity killer.
I think, a lot of third-party tools with third-party servers can scale much better and might work independent of each other. With Git underlying all these "third-party" tools can benefit from that "offline" approach, by just fetching the needed data "once" and then rely on its local/cached copy.
They don't need to DoS-attack the RTC-Server again and again, just because you opened a work item (to get all builds and change-sets) or open a review or "clicked somewhere" or or.
page 2of 1 pagesof 2 pages
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Sep 21 '23, 3:49 a.m.I considered this as one of the typical old (from 2013) questions that get answered with questions years after they were asked and closed it. I reconsidered it. This is probably a question that does not age. I will however accept the answer.
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Sep 21 '23, 6:59 a.m.David and I seem to disagree here 8)