Running distribution without a dedicated distribution team
A completed migration for an enterprise technology & software organization from Pulp.
- Company size
- Enterprise
- Industry
- Technology & Software
- Package formats
- Switching from
- Pulp
Technology stack
- Kubernetes
Before state
The customer ran its own instance of Pulp, an open-source, on-premises distribution solution, to publish and distribute a large and growing number of software artifacts across many operating systems and product versions. Maintaining it required a team of three senior engineers dedicated to day-to-day distribution, troubleshooting and optimization. Recurring outages, including one that left customers unable to download packages for two days, caused ongoing customer complaints about availability and uptime. Deploying custom builds for design partners was also cumbersome, with long lead times that limited the team's agility.
Pain points and value drivers
- Running a self-managed, on-premises distribution system required a team of three senior engineers dedicated to its upkeep.
- Recurring outages, including a two day outage that blocked customer downloads, generated repeated customer complaints.
- Deploying custom builds for design partners required long lead times and cumbersome reconfiguration.
Outcomes
- Freed up three engineering headcounts previously dedicated to running the self-managed distribution system.
- Eliminated customer complaints about availability and uptime after moving distribution to Cloudsmith.
- Distributes over 7,000 packages and 600GB of artifacts globally across 600 points of presence, with about 21,000 downloads a month.
- Simplified the release of custom builds for design partners, with no lead time for reconfiguration.
In their words
“Cloudsmith is key to our CI/CD and DevOps stack now. It should be a tool in the DevOps toolkit for everyone.”
“When my engineers tell me that they love a vendor, then I know not to question further. You can't get a harsher critic than an engineer, and our engineers love Cloudsmith.”
“I have literally saved three whole headcounts here. That is a major savings. Our three engineers who were mostly taking care of our distribution problems have now been redistributed into other areas. I actually do not have a software distribution specialist in my organization anymore. We just have our regular development teams that just continue working and building, and Cloudsmith just does its work.”
“Once we got the bulk of our assets moved from Pulp into Cloudsmith, we saw an instant drop in escalations. We used to get complaints from customers about availability, uptime of our distribution mechanisms, and their ability to reach and download images. Post the Cloudsmith switch, the complaints have literally gone to zero.”