Isn’t the sweet spot a combination of AP and CP for different parts of the same problem?
Arguably that’s what Slicer implements. It’s AP for high traffic routing requests that use it, and CP for slower decision making.
Same could be said for things like FoundationDB (and I’d guess Spanner) – topology in CP, “customer activity” in AP, resulting in a system that degrades very gracefully. A bit of a simplification, but I think it’s a good model for services like this.
Arguably that’s what Slicer implements. It’s AP for high traffic routing requests that use it, and CP for slower decision making.
Same could be said for things like FoundationDB (and I’d guess Spanner) – topology in CP, “customer activity” in AP, resulting in a system that degrades very gracefully. A bit of a simplification, but I think it’s a good model for services like this.