How Google migrated billions of lines of code from Perforce to Piper

Re:How Google migrated billions of lines of code from Perfor... by daemin on Monday July 01, 2024 @03:56AM (#40843526)

Nothing preventing you from building a versioned configuration system using a database or similar, especially if you build tools to actually change the configuration rather than hand editing text files.

[ Parent | on HN ]

Re:How Google migrated billions of lines of code from Perfor... by rockwotj on Monday July 01, 2024 @04:21AM (#40843657)

Google has this, IIRC it’s called CDPush

[ Parent | on HN ]

Re:How Google migrated billions of lines of code from Perfor... by underdeserver on Monday July 01, 2024 @04:51AM (#40843842)

CDPush does versioning, canaried rollouts of... hand edited text files.

[ Parent | on HN ]

Re:How Google migrated billions of lines of code from Perfor... by ablatt89 on Monday July 01, 2024 @05:08AM (#40843927)

I believe CDPush still has some latency involved which would be slower than reading raw config data from a DB.

[ Parent | on HN ]

Re:How Google migrated billions of lines of code from Perfor... by kccqzy on Monday July 01, 2024 @03:55PM (#40849920)

CDPush does the pushing. It's not a database.

[ Parent | on HN ]

Re:How Google migrated billions of lines of code from Perfor... by acac10 on Monday July 01, 2024 @06:00AM (#40844220)

The key to this is machine AND human readable formats. That is why the text format of protobufs is such a good approach: - structured formats - declared schema - the parser to read the file is also a validity checker (at least for data types)

There are tools that do similar with JSON but none are as simple and unobtrusive as protobuf tool chain.

[ Parent | on HN ]