Tom Coupland discusses some of the various technologies investigated, and in many cases deployed at Nokia including Gradle, Spring, MongoDB and Clojure.
Randy Shoup details some of the pieces forming Google’s technology stack, BigTable, Megastore, Dremel, virtualization, etc. and the design principles of their their cloud-based applications.
Tony Tam shares tips for modeling data with MongoDB for a fast and scalable system based on his experience migrating billions of records from MySQL to MongoDB.
Ian Robinson discusses the complexity of highly connected data and how graph databases can help, illustrating the talk with practical examples implemented using Neo4j.
Stefan Armbruster discusses building a Grails application with a graph data store based on Neo4j and sharing insight based on his own experience using such a system in production.
Andy Gross reflects on five years of involvement with Riak and distributed databases and discusses what went right, what went wrong, and what the next five years may hold for Riak.
Shanley Kane discusses Dynamo - consistent hashing, vector clocks, hinted handoff, gossip protocol - advances in each area, and how querying and application development has changed as a result of them.
Charles Cai, Ashwani Roy discuss a robust, cost effective, hypothetical solution to address extreme challenges in financial institutions, from decision making support to pricing and risk management.
Matt Asay outlines the reasons for NoSQL's existence and persistence, and will identify the trends that point to a bright future for post-relational databases.
Jim Webber explores graph data analytic techniques using social graph properties inspired by anthropology and sociology, extracting online business intelligence from graph matching.
Kenny Gorman provides advice on designing systems using MongoDB in order to avoid some of the pitfalls lurking along the way.
Adrian Cockcroft presents Netflix globally distributed architecture, the benchmarks used, scalability issues, and the open source components their implementation is based upon.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
- 10 Things Developers Should Know about Couchbase
- When one is better than two: Collapsing data management layers for scalability and simplicity
- Couchbase NoSQL @ Tunewiki : A billion documents and counting
- The Essential Couchbase APIs Cheat Sheet
- Why MySQL 5.6 is no real threat to NoSQL
- How to Move from MySQL to Couchbase Server 2.0: Part 1
- Making Sense of NoSQL
- Couchbase in Action – Real world app demo
- Making the Shift from Relational to NoSQL