Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Josh Alternatives
Similar projects and alternatives to josh
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
scalar
Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer (by microsoft)
-
monorepo.tools
Your defacto guide on monorepos, and in depth feature comparisons of tooling solutions.
-
-
-
-
-
josh
Discontinued Just One Single History [Moved to: https://github.com/josh-project/josh] (by esrlabs)
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better josh alternative or higher similarity.
josh reviews and mentions
Posts with mentions or reviews of josh.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-02.
- GitHub – josh-project/josh: Just One Single History
-
Debian Git Monorepo
Why use submodules when you can properly vendor the upstream git, and export/import commits without breaking hashes on either side?
https://github.com/josh-project/josh
We've been using josh at TVL for years and it's just amazing.
- Josh: Just One Single History
- Just One Single History
- Metahead – An enterprise-grade, Git-based metarepo
-
PyPy has moved to Git, GitHub
Scalar explicitly does not implement the virtualized filesystem the OP is referring to. The original Git VFS for Windows that Microsoft designed did in fact do this, but as your second link notes, Microsoft abandoned that in favor of Scalar's totally different design which explicitly was about scaling repositories without filesystem virtualization.
There's a bunch of related features they added to Git to achieve scalability without virtualization. Those are all useful and Scalar is a welcome addition. But the need for a virtual filesystem layer for large-scale repositories is still a very real one. There are also some limitations that aren't ideal; for example Git's partial clones IIRC can only be used as a "cone" applied to the original filesystem hierarchy. More generalized designs would allow mapping any arbitrary paths in the original repository to any other path in the virtual checkout. Tools like Josh can do this today with existing Git repositories[1]. That helps you get even sparser and smaller checkouts.
The Git for Windows that was referenced isn't even that big at 300GB, by the way. Game studios regularly have repositories that exist at multi-terabyte size, and they have also converged on similar virtualization solutions. For example, Destiny 2 uses a "virtual file synchronization" layer called VirtualSync[2] that reduced the working size of their checkouts by over 98%, multiple terabytes of savings per person. And in a twist of fate, VirtualSync was implemented thanks to a feature called "ProjFS" that Microsoft added to Windows... which was motivated originally by the Git VFS for Windows they abandoned!
[1] https://github.com/josh-project/josh
[2] https://www.gdcvault.com/play/1027699/Virtual-Sync-Terabytes...
- Just One Single History – combine the advantages of monorepos with multirepos
-
Kubernetes Broke Git
Good overview, I know these sorts of pains well. Lots of hard questions and few definitive wins/right answers. How to organize a massive repository out in the open is still an open question. On that note, recently, I've been experimenting with this project called josh, which basically is like 'git subtree on extreme steroids, functioning as a git proxy':
https://josh-project.github.io/josh/
It basically lets you unify/view many repositories as a single one, or equivalent to split a mono-repo into smaller sized units of work for CI, specific teams, etc. It's bidirectional, so you push and pull from josh and everything goes into a single linear history in the mono repo. And because it's bidirectional, people in the mono-repo can still do things like make large-scale atomic changes across all sub-repositories, and those get reflected.
Josh currently isn't suitable for a lot of workloads due to various reasons (authentication is one that stands out), but it's actually the first tool I have seen that manages to offer BitKeeper-like "subtrees" that work really well, at scale, for large repos and teams. It requires some care to make sure "sub-trees" can be usable units of work, but it was one of the best features of BK in my opinion and really great for people doing one-off contributions, or isolating trees/changes to specific developers.
I'd be interested to know if there are other open alternatives to this. It's a nice point in the design space between solutions like "integrate with the filesystem layer to do sparse clones" or "just split up the repos."
-
What Comes After Git
With regard to repo composition, I have been following this project: https://github.com/josh-project/josh
-
A note from our sponsor - InfluxDB
www.influxdata.com | 22 Apr 2024
Stats
Basic josh repo stats
21
1,326
7.5
15 days ago
josh-project/josh is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of josh is Rust.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com