• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Svccg nosql 2011_v4
 

Svccg nosql 2011_v4

on

  • 9,581 views

My presentation with bonus slides that I did not cover.

My presentation with bonus slides that I did not cover.

Statistics

Views

Total Views
9,581
Views on SlideShare
7,915
Embed Views
1,666

Actions

Likes
26
Downloads
0
Comments
1

7 Embeds 1,666

http://knight76.tistory.com 1637
http://www.linkedin.com 15
http://blog.sahsu.mobi 6
https://www.linkedin.com 5
http://twitter.com 1
https://abs.twimg.com 1
https://twitter.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Excellent presentation for db guys who are not yet on NoSQL Boat.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Existing functionality needs to move in phasesLimits the risk and exposure to bugsLimits conflicts with new product launches
  • Existing functionality needs to move in phasesLimits the risk and exposure to bugsLimits conflicts with new product launches
  • Existing functionality needs to move in phasesLimits the risk and exposure to bugsLimits conflicts with new product launches
  • Existing functionality needs to move in phasesLimits the risk and exposure to bugsLimits conflicts with new product launches
  • Existing functionality needs to move in phasesLimits the risk and exposure to bugsLimits conflicts with new product launches
  • Dynamo storage doesn’t suffer from this!
  • This is an issue with any SQL-like Query layer over a Sparse-data model. It can happen in other technologies.
  • Cannot treat SimpleDB like a black-box for performance critical applications.
  • We found the write availability was affected by the right partitioning scheme. We use a combination of forwarding tables and modulo addressing
  • Mention trickle lift
  • Dynamo storage doesn’t suffer from this!