Let's say you're working in a restaurant...
You, as a chef, don't wanna take the recipes from other chefs and cook it by yourself everytime you wanna create that delicious plate (that needs many recipes).
You would love if you had a kitchen that serves some ready-to-eat commodity food and compose it into your special plate.
Now, the lovely thing about that kitchen is that it keeps old commidity food with labels because some chefs prefer the old taste of that commodity food, and the kitchen is only allowed to enter for the chefs of that restaurant (because you don't wanna share your trade secrets with other restaurants).
Now change the above story wording:
Restaruant = your organization
Chefs = other developers/teams in your organizations
Recipe = package code (raw)
Kitchen = registry
Commodity food = packages (ready to be consumed)
Plate = your app
Labels = versions of those packages (to ensure new version won't affect apps using previous version of that package)
So something like a local maven repository (artifactory, nexus,...) instead of using maven central?
I'm not familiar with Java tooling, but I read about it and it seems like nexus.
If you're familiar with docker it's like a docker registry.
I think the unique value here is that it's a cloud based solution from the mighty Github.
Both sonatype (makers of maven, Nexus, and maintainers of central report) and jfrog (makers of artifactory) have cloud based solutions.
But they are mostly not gratis.
A good analogy and precisely why I'm looking forward to it.
So isn't it like npm registry?
Yes, it is like npm registry...
But, they say it supports all shapes and colors of registries (npm, maven, nuget... etc).
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.