News for hackers. Stuff that matters.
Re:Introducing Cloud Spanner, a Global Database Service by amalag on Tuesday February 14, 2017 @02:54PM (#13646567)
What is the monetisation plan? Purely SAAS with on-premise or an open source version with support like postgres/mysql?
Re:Introducing Cloud Spanner, a Global Database Service by evanweaver on Tuesday February 14, 2017 @03:24PM (#13646783)
The serverless cloud is pay-as-you-go. There is no minimum spend, unlike Spanner's $1000 per month (apparently). And it's cheaper than operating any open source on cloud hardware.

On-premises is licensed by core.

We have a developer edition you can use on your local machine, but we don't currently have plans to open source FaunaDB itself.

Re:Introducing Cloud Spanner, a Global Database Service by rgrove on Tuesday February 14, 2017 @05:15PM (#13647745)
Where did you read that Cloud Spanner has a $1,000 per month minimum spend? I can't seem to find any mention of this.
Re:Introducing Cloud Spanner, a Global Database Service by arjunnarayan on Tuesday February 14, 2017 @05:48PM (#13648036)
Minimum 3 nodes * node pricing of $.90/hour = 30.924*30 = 1944/month.
Re:Introducing Cloud Spanner, a Global Database Service by rgrove on Tuesday February 14, 2017 @06:07PM (#13648155)
Where is this 3-node minimum mentioned? URL please?

Edit: Looks like maybe you're referring to the recommended 3 node minimum in production mentioned at https://cloud.google.com/spanner/docs/instance-configuration

Re:Introducing Cloud Spanner, a Global Database Service by edaemon on Tuesday February 14, 2017 @09:21PM (#13649192)
While I'm not familiar with Spanner's inner workings, I would guess that they recommend 3 instances for quorum establishment in case a region becomes unreachable. If that's the case, using fewer than 3 instances could cause major problems.
Re:Introducing Cloud Spanner, a Global Database Service by dragonwriter on Wednesday February 15, 2017 @01:05AM (#13650084)
Since Spanner currently only supports single-region deployments, it clearly isn't recommended as protection against a region becoming unavailable.

It may be recommended as protection against an availability issue on an instance, though, which is, after all, a big reason why you'd want a distributed DB in production.

Re:Introducing Cloud Spanner, a Global Database Service by edaemon on Wednesday February 15, 2017 @12:41PM (#13653765)
I suppose the loss of a region doesn't apply (yet), but yes, the quorum requirement would still apply even if you only had instances in a single region.
Re:Introducing Cloud Spanner, a Global Database Service by inlined on Wednesday February 15, 2017 @02:34AM (#13650380)
Even within a single region you can put three nodes in different zones.