4 ms·
> I can’t even imagine what is going on from a technical level. I always wonder if most SaaS providers are fixated on building massive systems when simple shar
by donmcronald 5y ago
> I can’t even imagine what is going on from a technical level.
I always wonder if most SaaS providers are fixated on building massive systems when simple shards would work for most customers. If you compare something like Gitea and GitHub you can probably see the reason. With Gitea your "shard" is siloed away from everyone else because there's no federation (yet?). GitHub is more like a huge social network where everyone can interact.
I think the vision for a lot of SaaS is to facilitate B2B collaboration by acting as a proprietary social network rather than via federation between relatively independent shards. The reason is simple IMO; vendor lock-in.
- media-trivial 5y agoFormer Gitea (Gogs) contributor here. I see your point and you're not really wrong but it's not that easy either: - GitHub has way more features. More features means more scattered data (e.g. different micro-services databases, file storage). - You cannot use Gitea in an organization with hundreds or thousands of engineers. It provides nether the features nor the scalability you need. I like Gitea but I'm happy that my company uses GitHub. - Individuals and open-source use GitHub because it's free and has all the features (including stuff like free CI/CD which is expensive). This is all being paid for by companies like mine who buy expensive enterprise licenses for thousands of engineers. - It's not uncommon to shard by customer/account, even in the cloud and GitHub is actually trying to do this right now for their primary database. Doesn't solve the problem with different storages for different micro-services though.