From NoSQL to Mo' SQL in Riak [Video]
From NoSQL to Mo' SQL in Riak [Video]
Those familiar with Riak might know it as a NoSQL solution. But this presentation shows how to it's starting to incorporate that classic SQL feel in a couple of ways.
Join the DZone community and get the full member experience.
Join For FreeDiscover Tarantool's unique features which include powerful stored procedures, SQL support, smart cache, and the speed of 1 million ACID transactions on a single CPU core!
The Basho team of distributed systems engineers continues to develop new Riak functionality to help companies build innovative applications. A few members of the Basho team recently took a break from their day jobs to share some of the details of their recent work at the Erlang User Conference in Stockholm. In case you missed them, we wanted to share videos of these presentations. (Hint: They aren’t just for people passionate about Erlang)
Gordon Guthrie showed how NoSQL really means “not only SQL” and explained the new capabilities and techniques in Riak that are specifically optimized for time series data.
From NoSQL to Mo' SQL: Adding Structure and Queriability to Riak
Speaker: Gordon Guthrie, Senior Engineer at Basho and Serial Entrepreneur
GitHub: gordonguthrie Twitter: @gordonguthrie
Presentation Overview
With the new Riak Time Series, you're seeing more traditional tools like native SQL querying being added. This talk will look at meta-programming being used in a gossip-based cluster to build an adaptive Riak that reconfigures itself to handle structured data — and how we use standard SQL to interrogate that data.
Discover Tarantool's unique features such as powerful stored procedures, SQL support, smart cache, and the speed of 1 million ACID transactions on a single CPU.
Like This Article? Read More From DZone
Published at DZone with permission of Dorothy Pults , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}