Live data from Hacker News

Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

highscalability.com

61–70 of 82 posts

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#61

It's really funny to watch tech journalists try to write about Google infrastructure from the outside, based only on one paper... Hell, it's usually really funny just to watch tech journalists try to write.

Web programmers take note: High Scalability == Tech Journalism.

The sad part is web programmers think these blogs are some sort of programming advice. "What is your stack?" == "I am an idiot."

How does it feel to "kickstart a revolution" (those are Mr. High Scalability's the exact words) every time you publish a paper?

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#63
So the correct and responsible thing for Google to do now would be to patent the shit out of this and then sue back into the stone age anybody that implements anything even vaguely similar, right?

I mean, the social fabric depends on companies protecting their innovations, right?

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#64
post #36

Earlier quoted context omitted.

It is ACID. It is a DBMS. It's not a Relational DBMS.

Dude its a pun :-)

We just need to name a drug "DBMS" (preferably something that makes you feel emotionally close, hence "relational DBMS") to complete the pun.

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#65
post #51

It's really funny to watch tech journalists try to write about Google infrastructure from the outside, based only on one paper... Hell, it's usually really funny just to watch tech journalists try to write.

High Scalability is a serious and informative blog, and I wouldn't dismiss it. This isn't TechCrunch. Its focus is less on rigorous scientific analysis of a narrow field, but a good, moderately deep, overview of anything to do with data scaling. And it's doing a darn good job.

It's funny because it's technically a violation of an NDA.

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#67
post #6

Earlier quoted context omitted.

So your saying its not ACID its more like Ecstasy?

Ecstasy might work: Eternally Consistent State, Transactions And Scale, Yes please.

Very well done, sir.

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#68
post #13

This article comes across as really cynical and entirely lacking in the kind of rigor and detail I have previously found on highscalability. Spanner is really mind-blowingly cool tech. I thought this article was much more informative and worth the time to read: http://news.ycombinator.com/item?id=4562546

I think the notes about transactions are quite valid as the point of a HS post. However the author didn't have anything else to add ("I look forward to more insightful commentary. There’s a lot to make sense of") yet felt the need to keep writing, and filled the article with style and attitude rather than substance.

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#69
"A complicating factor for an Open Source effort is that Spanner includes the use of GPS and Atomic clock hardware." (!)

Can anyone explain why such an accurate clock is helpful? I can see that it's needed if you create a document on the East Coast at about the same time as you create a document on the West Coast, and you absolutely need to know which was created first, but for most applications can't you just go with whatever time the system that got the insert thinks it is??

Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

#70
post #69

"A complicating factor for an Open Source effort is that Spanner includes the use of GPS and Atomic clock hardware." (!) Can anyone explain why such an accurate clock is helpful? I can see that it's needed if you create a document on the East Coast at about the same time as you create a document on the West Coast, and you absolutely need to know which was created first, but for most applications can't you just go wit…

> for most applications

I suspect that part of the point is that this application does care.

Post reply on HN