4/4 #NoSQL does require a bit more planning and better design than #SQL

Tip: Maximise the power of NoSQL by storing your data based on how you intend to query it!

Give NoSQL a try with #OpenRiak

Check it out here: github.com/openriak

3/4 #NoSQL can do something that #SQL can’t do efficiently—run multiple parallel GET operations

A complex SQL statement joining multiple tables is just a bunch of parallel GET operations in NoSQL

These run in parallel, so the slowest operation determines the total query time

2/4 #NoSQL is like a filesystem, letting you store anything in any format

Take user info, with NoSQL you could store:

- Username as text
- Profile picture as a JPG
- Address as a JSON blob
- Password as a hash

Because of this #NoSQL runs rings around #SQL for direct lookups

4/4

Join the growing community

Contribute to #OpenRiak via Github at github.com/openriak

#NoSQL #SoftwareDevelopment #Database

3/4

OpenRiak puts the onus on developers to write smart queries. It's designed by top developers for top developers. Why not raise your game to work with the best?

2/4

This direct access enables far more powerful and efficient queries to be planned and executed using #OpenRiak, as they don't need to run through unnecessary intermediary layers...