by gregyoung
by Ian Plosker
When building a distributed, NoSQL database, a lot of traditionally accepted theories and practices go out the window. The simple fact of building systems for distributed environments throws up many challenges that are not easily met with traditional software approaches. This session intends to take a deeper look at some popular use cases around Riak – delving deeper into the configurations and the trade-offs made by the users to insure success in a distributed environment. Attendees of this session will come away with a greater understanding of the flexibility of NoSQL solutions like Riak, as well as how Riak solves serious data problems in interesting ways, and learn where Riak might not
by Jim Webber
In this talk we'll take a broad look at NOSQL databases, including motivating similarities and more importantly their different strengths and weaknesses. In more depth, we'll focus on the characteristics of graph databases for managing connected data and the kinds of problem domains for which they are best suited. To reinforce how useful graph databases are, we provide a rapid, code-focussed example using Neo4j covering the APIs for manipulating and traversing graphs. We'll then use this knowledge to explore the Doctor Who universe, using graph databases to infer useful knowledge from connected, semi-structured data. We conclude with a discussion of when different kinds of NOSQL stores are most appropriate.
Kresten Krab Thorup, CTO of Trifork GmbH will be presenting compelling case study about A Matter of Life and Death data and a solution that has been used with an Electronic Danish Common Medicine Card - cloud based data platform designed to deliver on some tough requirements - RIAK.
The consistency model used by Riak is designed to continue operating well even when nodes in your Riak cluster are down or unreachable, a property which also makes it a good model for mobile data. To me, "down or unreachable" sounds a lot like "off or without-cell-phone-connectivity" - common states for a mobile device.
In this talk, I'll present Riak Mobile, a component that can be embedded into your iOS or Android application to make it a full Riak replication-aware peer. Typical usages for Riak Mobile is as a mobile content distribution platform using one-way sync; or with two-way sync to also push updated data back to your Riak cluster when the network is "eventually" available.
In the talk, I'll walk through how Riak Mobile works. The client-part of Riak Mobile does not require an Erlang VM. Rather, it comes as either a Java or an Objective-C component using SQLite for on-device storage, and thus integrates nicely into the native development environments. The server-part is an OTP application running with Riak. Riak Mobile uses a flow-based algorithm using Merkle trees and vector clocks optimized specifically for providing efficient incremental synchronization for slow, high-latency network conditions.
by Pavlo Baron
Amazon Dynamo paper has desrcibed a special use case oriented and actually working in practice subset of ideas and concepts which are as old as the Bavarian forest. I will explain where they came from, reference the origins, and also explain these concepts in technical depth as well as why this extract from the distributed systems theory was necessary for its special use case.
Once you begin developing with NoSQL technologies you will quickly realize that accessing data stores or services often requires in-depth knowledge of proprietary APIs that are typically not designed for use in enterprise Java applications. Sooner or later you might find yourself wanting to write an abstraction layer to encapsulate those APIs and simplify your application code. Luckily such an abstraction layer already exits: Spring Data.
In 2010 SpringSource launched an umbrella project called Spring Data that makes it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud-based data services. Spring Data also provides enhanced support for conventional relational database technologies.
In this talk, Patrick Baumgartner will demonstrate to attendees how to easily leverage NoSQL data stores like MongoDB, Neo4j, and others using Spring Data.