Artwork

Content provided by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Episode 123: NoSQL

15:52
 
Share
 

Manage episode 156001529 series 1173626
Content provided by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Find out what NoSQL is and isnt.

News and Follow/Ups – 02:24

Geek Tools – 13:15

Webapps – 15:22

NoSQL – 19:56

  • What are they?
    • Usually don’t require fixed table structures
    • Usually used to scale horizontally
      • Add more commodity nodes as opposed to adding more resources and using expensive hardware
  • Why would you use them?
    • Scalability
    • Performance
    • In certain use cases they are easier to implement
  • When would you NOT use them?
    • If you don’t know ahead of time how you are going to query or data
      • Applies mainly to key-value type NoSQL
    • Usually arguments start because people think in terms of RDBMS vs NoSQL. They are usually implemented side by side for difference use cases. It is not an all or nothing.
  • CAP Theorem
    • Consistency (all nodes see the same data at the same time)
    • Availability (node failures do not prevent survivors from continuing to operate)
    • Partition tolerance (the system continues to operate despite arbitrary message loss)
    • Cap Theorem says that a system can satisfy two of these but not all three.
  • Popular DocDBs
  • Key-value based
    • Redis
      • Blizzard
      • Stackoverflow
      • Github
      • Tweetdeck
    • Memcached
      • Just about everyone, although many people are moving to redis
    • Cassandra
      • Cisco
      • Cloudkick
  • Column oriented
  • Graphdb
    • neo4j
      • Good at multiple relationships
        • Think product categories
        • User friend follow relationships
      • Amazon

  continue reading

10 episodes

Artwork

Episode 123: NoSQL

Faceoff Show

published

iconShare
 
Manage episode 156001529 series 1173626
Content provided by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jade Robbins and Mark Sanborn, Jade Robbins, and Mark Sanborn or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Find out what NoSQL is and isnt.

News and Follow/Ups – 02:24

Geek Tools – 13:15

Webapps – 15:22

NoSQL – 19:56

  • What are they?
    • Usually don’t require fixed table structures
    • Usually used to scale horizontally
      • Add more commodity nodes as opposed to adding more resources and using expensive hardware
  • Why would you use them?
    • Scalability
    • Performance
    • In certain use cases they are easier to implement
  • When would you NOT use them?
    • If you don’t know ahead of time how you are going to query or data
      • Applies mainly to key-value type NoSQL
    • Usually arguments start because people think in terms of RDBMS vs NoSQL. They are usually implemented side by side for difference use cases. It is not an all or nothing.
  • CAP Theorem
    • Consistency (all nodes see the same data at the same time)
    • Availability (node failures do not prevent survivors from continuing to operate)
    • Partition tolerance (the system continues to operate despite arbitrary message loss)
    • Cap Theorem says that a system can satisfy two of these but not all three.
  • Popular DocDBs
  • Key-value based
    • Redis
      • Blizzard
      • Stackoverflow
      • Github
      • Tweetdeck
    • Memcached
      • Just about everyone, although many people are moving to redis
    • Cassandra
      • Cisco
      • Cloudkick
  • Column oriented
  • Graphdb
    • neo4j
      • Good at multiple relationships
        • Think product categories
        • User friend follow relationships
      • Amazon

  continue reading

10 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide