"So GoshawkDB doesn't have an SQL engine currently, so in that way it's probably not comparable with F1. GoshawkDB stores and accesses an object graph. Hopefully the howtos on the website will help people get into the mindset."
Gotcha.
"I'm not sure if it's worth trying to compare anything to Spanner or F1 because unless I'm mistaken, no one outside of Google can use F1 or Spanner - they're not released. So who knows what the performance of these things actually is? There's no way to verify the claims made in any Google paper."
I think it's worthwhile for these reasons:
1. They describe it in enough detail in their papers for comparisons or maybe clones to be made.
2. That's led to competitors or open-source clones of tech before. Remember map reduce?
3. They've deployed it operationally.
4. Since when can Google not handle a backend tech it claims to be able to do? I thought their rep was solid on that stuff.
So, Google already as a strongly-consistent, scalable, multi-datacenter RDBMS with NoSQL-like performance. If good on enough workloads, that's the best thing I've heard in that category since NonStop SQL. The GPS thing, while brilliant hack, might be hard for adoption. An improvement area CochroachDB people are already targeting. A full clone or competitor could rock DB world as a great alternative to Oracle clusters or NonStop for mission-critical workloads where some delays were tolerable.
Gotcha.
"I'm not sure if it's worth trying to compare anything to Spanner or F1 because unless I'm mistaken, no one outside of Google can use F1 or Spanner - they're not released. So who knows what the performance of these things actually is? There's no way to verify the claims made in any Google paper."
I think it's worthwhile for these reasons:
1. They describe it in enough detail in their papers for comparisons or maybe clones to be made.
2. That's led to competitors or open-source clones of tech before. Remember map reduce?
3. They've deployed it operationally.
4. Since when can Google not handle a backend tech it claims to be able to do? I thought their rep was solid on that stuff.
So, Google already as a strongly-consistent, scalable, multi-datacenter RDBMS with NoSQL-like performance. If good on enough workloads, that's the best thing I've heard in that category since NonStop SQL. The GPS thing, while brilliant hack, might be hard for adoption. An improvement area CochroachDB people are already targeting. A full clone or competitor could rock DB world as a great alternative to Oracle clusters or NonStop for mission-critical workloads where some delays were tolerable.