3 ms·

Very cool. I haven't read the whole paper yet, but from a quick overview it seems somewhat similar to SLOG (which also deals with world-scale replication by try

by maxmcd 7y ago

Very cool. I haven't read the whole paper yet, but from a quick overview it seems somewhat similar to SLOG (which also deals with world-scale replication by trying to keep data closer to the nodes that use it): - http://www.vldb.org/pvldb/vol12/p1747-ren.pdf http://www.vldb.org/pvldb/vol12/p1747-ren.pdf - https://blog.acolyer.org/2019/09/04/slog/ https://blog.acolyer.org/2019/09/04/slog/ Any thoughts on this comparison?

mjb 7y ago
Very interesting, I hadn't seen SLOG before. It seems like there's a fairly similar core insight: placing data near where it's used can help with some system properties. They appear to be more latency-focused and we were (primarily) aiming at availability. The other different part of Physalia is our focus (again, for availability) on placement for 'blast radius'. That means we try limit the number of cells than any one failure (software, infrastructure, etc) can touch. Geo-replicated systems can have similar concerns, but I haven't seen the same level of focus on it as a key design goal.