DevOps in Action: Feed Replication supporting true collaboration
As mentioned in my previous post , multi-site replication is the mirroring of feeds across multiple ProGet instances. Many of our ProGet Enterprise users have a scenario that requires common components, yet their instances are in different geographic locations. Recently, one of our users described their set up of replication, and how, although not geographically dispersed, they still found a huge benefit from implementing replication.
One organization. Separate teams. Common packages.
Different teams within an organization may require separate instances of their package manager. Take for example an industry that has strict regulations, or specific security processes, like banking. A bank may have three separate instances of ProGet: Mortgages, Franchises, and Wealth Management, all “owned” by the corresponding business unit. While all are located in the same place, their instances are kept separate for regulatory purposes. Common packages may still need to be accessed by the three business units (such as branding materials like logo files, style guidelines, etc.) By creating a replicated feed across these instances, all business units will then have access to the necessary assets, while still being able to maintain their individual ProGet instances. If Franchises uploads a package to the replicated feed, Mortgages and Wealth Management will mirror that change, and will then also have access to the same package in their feed. This example is reflected in the dark blue feed below.
They are also able to replicate between specific instances. This is especially useful when rolling out a feature one business unit at a time. In the above example, Franchises rolls out the feature first, then Mortgages, and eventually Wealth Management. However, say the organization has decided that Wealth Management is not ready to implement the feature, and therefore doesn't have access to the replicated feed. This is reflected in the Orange feed above.
Feed Replication Across a Common Location
Regardless of why you need feed replication, it’s a useful feature that helps enterprises stay organized, and ensures stability and uniformity across all teams and locations. It can be implemented in different ways, and with different use cases; but can be critical to your software development process, and creating cohesion among multiple internal teams, or across geographically diverse offices.
Already a ProGet Basic user but want to take advantage of this feature? Reach out to our team here for an upgrade quote!