Sweden’s Next Top NoSQL Data Model


By Erlang Central | Published: May 28, 2012



Data modeling is hard, especially in the world of distributed NoSQL stores. With relational databases, developers have tended to store normalized data and shape their query model around that structure. This can come back to bite you when it comes time to scale, as complex queries across dozens of tables begin to affect application performance. It’s common to find developers rethinking their data model as query latency increases under load.

With NoSQL stores, developers must consider their query patterns from the outset of application development, designing their data model to fit those patterns. A number of techniques, new and old, can be used to allow for maximum performance and scalability.

Topics covered will include:
De-normalization, time boxing, conflict resolution, and convergent & commutative replicated data types. Additionally, discussions of common query patterns in light of the capabilities of various NoSQL data stores will be reviewed.

Talk objectives:
To enable developers to understand that the data model must follow query patterns when using a NoSQL storage solution.

Target audience:
Developers using or thinking about using a database, be it relational or NoSQL. Anyone interested in distributed systems.


Download Presentation Download

Speakers:

  • Ian Plosker

    Developer Advocate, Basho Technologies
    Basho Technologies

    Ian Plosker is the Technical Lead, International Operations at Basho Technologies, the makers of the open source database Riak. He has been developing software professionally for 10 years and programming since childhood. Prior to working at Basho, Ihedeveloped on everything from CMS to bioinformatics platforms to corporate competitive intelligence management systems. At Basho, he's been helping customers be incredibly successful using Riak.

    Favourite quote: "Truth is the most valuable thing we have. Let us economize it." - Mark Twain

    Ian Plosker


Follow Erlang Central:


Have an Erlang Question?

Reach out to the Erlang community





Tags