Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
highscalability.com
Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
1–10 of 82 posts
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#2NewSQL ? Seriously ? Do we really need another low-quality buzzword for people to re-use everywhere ?
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#3NewSQL ? Seriously ? Do we really need another low-quality buzzword for people to re-use everywhere ?
I don't know, I think it's helpful. It changes the conversation from being about the access language to being focused on how a technology processes data at scale. Well, almost...
Notice that even with the shift from "NoSQL" to "NewSQL", mentions of joins continues to be conspicuously absent from many of these discussions. So, it's worth noting that many of these NewSQL things are "almost but not quite SQL", hence the value of a new word.
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#4NewSQL ? Seriously ? Do we really need another low-quality buzzword for people to re-use everywhere ?
I think there should be a term for these new DBMSs, but the problem with NewSQL is that the thing they have in common is not SQL, but consistency and transactions.
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#5So is Spanner basically just a distributed mostly-relational database? It seems like to find the record you want you just search the indices of nodes like a B-tree and in a couple queries are left at the node with the records you want. The downside is all that lost write performance but since it's synchronous you can probably mitigate some of the rebalancing by having many indices of indices, so only a couple nodes have to actually rebalance anything on a write.
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#6NewSQL ? Seriously ? Do we really need another low-quality buzzword for people to re-use everywhere ?
I think there should be a term for these new DBMSs, but the problem with NewSQL is that the thing they have in common is not SQL, but consistency and transactions.
So your saying its not ACID its more like Ecstasy?
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#7"Maybe this time Open Source efforts should focus elsewhere, innovating rather than following Google?"
There's a ton of innovative projects in the open source community, but it's difficult to convince people to use them. Developing a clone of a Google tech has a built in marketing advantage: "Google uses something like this."
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#8Earlier quoted context omitted.
I think there should be a term for these new DBMSs, but the problem with NewSQL is that the thing they have in common is not SQL, but consistency and transactions.
So your saying its not ACID its more like Ecstasy?
Ecstasy might work:
Eternally Consistent State, Transactions And Scale, Yes please.
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#9With some of the best programming minds in the world, it's interesting to see that Google finds it more efficient for programmers to solve the performance issues vs reimplementing core db functionality, such as transactions.
I like the direction of moving closer to original database theory concepts and allowing the creative energy to focus on solutions to performance problems at high-scale.
Re: Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In
#10I am in favor of any label that replaces "NoSQL" with something else. NoSQL always rubbed me the wrong way. Besides not being a huge fan of the "No", it really says nothing about what it is(if it isn't SQL).