Binary repository manager: Difference between revisions

Revision as of 21:25, 18 February 2016

Revision as of 05:34, 19 February 2016

Line 1:

A '''binary repository manager''' is a software tool designed to optimize the download and storage of binary files used and produced in software development. It centralizes the management of all the binary artifacts generated and used by the organization to overcome the complexity arising from the diversity of binary artifact types, their position in the overall workflow and the dependencies between them.

Line 57 ⟶ 55:

==Universal Package Manager==

The software and technology industry continues to change and grow, binary repository managers are no different. They are beginning to shift towards positioning as a universal package managers.<ref> {{cite web |url= https://adtmag.com/articles/2015/09/08/jfrog-repository.aspx |title= JFrog Releases ‘Universal’ Artifact Repository |last=Waters |first= John K.| date= 8 September 2015|website=ADT Mag| publisher=Application Development Trends Magazine}}</ref>. These package managers aim to standardize the way enterprises treat all package types used in the [[software development process]]. They give users the ability to apply security and compliance metrics across all artifact types. Universal package managers have been referred to as being at the center of a [[DevOps]] toolchain.<ref>{{cite web |url= http://www.codeproject.com/Reference/628210/An-Overview-of-the-NuGet-Ecosystem | title=An Overview of the NuGet Ecosystem | last=Decoster | first=Xavier | date= 18 August 2013| website=CodeProject.com}}</ref>.

== Key features of repository Managers==

Key factors and features when consider the adoption of a package manager include: <ref>{{cite web |url= http://www.computerweekly.com/blogs/cwdn/2015/11/how-to-find-real-devops-look-for-binary-artifact-repository-control.html |title= How to find real DevOps, look for binary artifact repository control |last=Bridgewater | first=Adrian | date= 1 November 2015 |website=ComputerWeekly.com}}</ref>

*'''Caching''' – Caching simply stores local copies of packages. This increases performance for slow internet connections by allowing the user to pull from the local repository instead of externally. Caching locally allows frequently used packages to be available even during times of external repository outages.

*'''Caching''' – Caching simply stores local copies of packages. This increases performance for slow internet connections by allowing the user to pull from the local repository instead of externally. Caching locally allows frequently used packages to be available even during times of external repository outages.

*'''Retention policies''' - Repository managers can be used and configured to support organization purging policies to ensure reasonable disk space usage. Local repositories for third party artifacts may also be purged after not being used by any release for a specified time.

*'''License filtering''' - Third party artifacts may be subject to approval processes due to licensing and legal issues. Package manager allow for restriction of only approved artifacts into deployment.

*'''High availability''' - Since a binary repository manager maintains all the development dependencies, its vital to always maintain access to these artifacts.. Any down-time of the binary repository manager can halt development with all the significant consequences to the organization. A High Availability instance allows an enterprise to overcome the risk associated with downtime, through automatic failover. This is achieved by having a redundant set of repository managers work against the same database and file storage. Maintaining enterprise wide stability and performance at all times

*'''License filtering''' - Third party artifacts may be subject to approval processes due to licensing and legal issues. Package manager allow for restriction of only approved artifacts into deployment.

*'''User restrictions''' - Repository managers can be integrated with other organization systems such as LDAP or Single Sign-on servers to simplify and centralize user management. This gives an enterprise granular control over who has access to vital software components.

*'''High availability''' - Since a binary repository manager maintains all the development dependencies, its vital to always maintain access to these artifacts.. Any down-time of the binary repository manager can halt development with all the significant consequences to the organization. A High Availability instance allows an enterprise to overcome the risk associated with downtime, through automatic failover. This is achieved by having a redundant set of repository managers work against the same database and file storage. Maintaining enterprise wide stability and performance at all times

*'''User restrictions''' - Repository managers can be integrated with other organization systems such as LDAP or Single Sign-on servers to simplify and centralize user management. This gives an enterprise granular control over who has access to vital software components.

== Tools ==

Notable package mangers include: <ref>{{cite web |url= http://alternativeto.net/software/proget/ | title=ProGet |access-date=4 February 2016 | website=alternativeTo.net}}</ref>

* JFrog's Artifactory

* Apache Archiva