| ▲ | Git at Any Scale(cursor.com) | |
| 30 points by meetpateltech 13 hours ago | 3 comments | ||
| ▲ | biwills 7 hours ago | parent | next [-] | |
> What about consensus? Elections? Which server is the primary for a given repository? It also doesn't matter! There's no state and no consensus here. Any server can be the primary. All updates to the write-ahead log are synchronized with an atomic compare-and-swap (CAS) operation on S3, so it's always safe for any instance of a repository to receive a push. Again reminded of what an amaizing piece of engineering S3 is (99.999999999% - 11 nines of durability) [1] 1: https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDu... | ||
| ▲ | vegadw 11 hours ago | parent | prev | next [-] | |
Remember, don't put large objects in cnt, it makes it a real pain later. | ||
| ▲ | ChrisArchitect 12 hours ago | parent | prev [-] | |
Related: Cursor Origin Code Hosting | ||