We're hoping to add more compatibility layers, but the semantics of reading updates within a transaction are what gave the team pause. If you don't need that semantic, it's relatively straightforward (I assume we'll see this happen either directly by us, or from the community).
Disclosure: I work on Google Cloud, but not on Spanner.
Re:Cloud Spanner is now production-ready
by fdsfsafasfdas on Tuesday May 16, 2017 @03:27PM
(#14352483)
Any chance that Google Cloud will ever expose access to F1?
The point of the SQL layer now merged into Spanner is so that people don't have to run F1 or something like it on top. I'd expect continual improvements there, especially if enough folks say "I'll move if X"
Re:Cloud Spanner is now production-ready
by fdsfsafasfdas on Tuesday May 16, 2017 @04:16PM
(#14352916)
Well, the hope would be that it would allow read-write-read sql transactions, which to my understanding will never be implemented in Spanner.
Any insight into why read-write-read sql transactions will never make it into Spanner?
Not sure if "never", but from the new Spanner paper[1]:
> While we have seen comparatively little demand for this feature internally, supporting such semantics improves compatibility with other SQL systems and their ecosystems and is on our long-term radar.
Thanks for the clarification and the link.
Re:Cloud Spanner is now production-ready
by curiousDog on Tuesday May 16, 2017 @02:10PM
(#14351867)
Also important to note that it's a NewSQL system, not a full blown RDBMS. You can't lift and shift your MySQL application and expect full blown horizontal scalability and such.
I'm surprised no one has challenged this yet - if there is anything that cloud spanner does better than most things out there, it's "full-blown horizontal scalability"! There are very few systems out there that have tackled the issue of scaling beyond cross-AZ in a non-bullshit way.
I'd throw one downside out there though: lock in. While queries use standard SQL syntax [1], all write operations are performed via a very non-standard GRPC API [2]. I think the team certainly considered this and weighed the trade offs, but it does mean that after you're on Spanner, you're on Spanner forever.
[1] https://cloud.google.com/spanner/docs/query-syntax
[2] https://cloud.google.com/spanner/docs/reference/rpc/