Cloud hosting: The meaning of controlling source with SaaS

The most important technical decision about source control (SCC) is whether to host the repository in the engine room (on premises) or outside the engine room (off-premises).

Most developers focus on the technical details of the SCC protocol, which is equivalent to arguing Ford vs. GM, based on whether the battery and fuel are in the driver's side or on the passenger side. At the same time, Application Lifecycle Management (ALM) publications often focus on the list of advanced vendor performance, and the right accounts are neither for legacy requirements nor for new opportunities to expand cloud market offerings.

SCC is essentially a mature technology; Although smart programmers continue to create new conveniences, the basics are clear, as the original source control system was developed 40 years ago at Bell Labs. Most of the functionality can be translated between "gateways" or in the popular battle against SCC servers. There are enough incentives for mid-level administrators or programmers to "migrate" legacy repositories to new servers.

Developers are passionate about choosing an SCC model, especially when there are technical differences between these alternatives. At the same time, this level of operation is indeed a symptom of a deeper problem, with some exceptions, development enterprises frequently use advanced SCC performance, so that the work flows through complexity. The need for complex changes also includes emerging alternative branches.

Where do I host the repository? Who's going to maintain it? These are important strategic issues. Considering the correlation, the specific characteristics of SCC should be considered first.

What makes SCC so special?

SCC is a rare "value-added", even if the front-line coder most involved, need, just do some simple functions. SCC is considered a conservative term; it requires availability, predictability, and reliability. There's no need to overdo it--a successful business is usually based on a very small part of the source code, even as large as the operating system's core applies to the ipod corner.

Furthermore, as mentioned earlier, SCC has spread widely over the past 40 years. A large number of administrators are familiar with SCC management.

How do you expect them to arrange their time? While SCC administrators are not an important responsibility, it is a time-consuming task to ensure that backups, landings, free space, and so on are properly configured.

Although most ALM descriptions have not yet considered this possibility, the next generation of developers will think by default: they are thoroughly accustomed to relying on cloud services like GitHub or BitBucket.

SCC's entry into the cloud does not depend on other IT decision making in the enterprise. Whether you have an internal mail server or a mail service from a vendor, there is no effect on what is the right SCC. The source code is the core enterprise asset, but it is also the business document and project plan of the enterprise. Even if the security or availability of a decision is most important, it is not encouraged to determine the correct SCC. Because you still have to determine whether you can better manage the security risks of maintaining the SCC server, or through a contract with a specific vendor.

What is the essential basis for good management: document the specific SCC requirements, costs, and the benefits of different alternatives, what kind of disaster recovery each type of work uses, and make clear decisions. SCC is labeled as a necessary tool, the application of which covers a wide range and role in the enterprise, then you cannot assume the right decision for different teams and apply it automatically to your environment.

Finally, realize that with proper preparation, the SCC part of ALM is likely to succeed. The source code and modern server capabilities are relatively small, and you can easily experiment or mix different solutions. Your programmers need you most to define SCC plans so they can work and add value. They want to know how to (SCC technical terminology) and adopt it quickly, whether in the cloud or within their own enterprise.

(Responsible editor: The good of the Legacy)