Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why do other multi-site solutions force you to change development procedures while WANdisco doesn ?

0
Posted

Why do other multi-site solutions force you to change development procedures while WANdisco doesn ?

0

Ans. Other multi-site solutions that lack WANdisco’s real-time capabilities have a fundamental problem in that they can never guarantee that local and remote repositories will be in sync at any point in time. This means that there is a great likelihood that developers at different sites could easily clobber each other’s work. To prevent this, these solutions require excessive, error prone source code branching and file merging to become part of the development process. This effectively forces development work to be partitioned based on geography, and makes collaboration between distributed development teams virtually impossible. As a result, problems are not discovered until later in the development cycle resulting in more QA and rework. In addition, multi-site solutions that rely on master/slave architectures force developers to check out source code from the local repository, and check in their changes to the master. This often leads to inadvertent source code merging and check-in sn

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123