3 ms·
My guess: 1. The abstraction is not what most developers want. Colossus gives you append-only files, halfway between a file store and an object store. This i
by pclmulqdq 4y ago
My guess:
1. The abstraction is not what most developers want. Colossus gives you append-only files, halfway between a file store and an object store. This is not an abstraction that most developers are comfortable with. It also has a relatively thick client library, so if you were planning to have a "microservice" it is a lot to import. Both of these factors help to simplify the reliability story.
2. Open source users are generally used to picking the abstraction they want, then finding the thing that does it. In contrast, Colossus/GFS use is mandated at G.
3. Colossus's bugs were worked out due to scale, which means wide adoption. Ceph and Lustre, in contrast, tend to have relatively small installations (measured in TiB or single-digit PiB) and their maintainers have seen many fewer byzantine failures by consequence.
I have played with a SaaS offering of a similar service, but it's a huge project and I don't want Google to sue me. OSS would likely be completely off the table except as an "open core" type of concept - there is just too much engineering effort needed to get to the first version.
- amelius 4y ago> Colossus gives you append-only files, halfway between a file store and an object store. This is not an abstraction that most developers are comfortable with. Most of the files I use are append-only (or in fact write-once). The only files that are random-access are database files (but I prefer using the filesystem as an approximation to a database; not sure to what extent Colossus can serve that usecase; e.g. does it provide transactions?) Do you have other examples of files that are not append-only or write-once?
- pclmulqdq 4y agoBTrees for databases are the most important file types that you lose. Colossus/GFS is why Google adopted LSM trees (eg in LevelDB) instead of BTrees. Another example is documents (think .doc files), although these can also be log-structured or checkpointed (I think the .docx is almost 100% log-structured).
- jeffbee 4y agoI know what you meant but it might confuse people to say that it is append-only. Clients may read at any committed offset, otherwise it would be quite useless.