One year with mongo db klmug presentation

488 views

Published on

KLMUG presentation Nov 7

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
488
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Allows Mindvalley to iterate very fast No need to mess up with MySQL migrations
  • This was when we were still doing RnD on the different NoSQL dbs Joffrey - somewhat like Google Analytics MV uses Linode, setup a 32 bit server, suddenly no more data after 2GB
  • Schemaless allows you to change your mind easily at the beginning Once you have a lot of data, migrations are a pain
  • Dates are stored in Unix Time (milliseconds after epoch) No niceties with a real date store like DST and Timezones Dates before v2.0 were unsigned, so having a date before 1970 resulted in a rollover
  • JSON - makes it really easy Almost like SQL Language-specific DSL makes it easier
  • Tried many: RockMongo, MongoHub, etc. Management tools are still not that mature Export/Import, dumps, export to SQL/CSV/JSON -> command line still does it better
  • Mongoid
  • Story of slaves and replica set in Oathkeeper -> it went down, it didn’t failover, turns out the driver configuration was for slaves and not for replica sets
  • Rollbacks need to be coded at the client level
  • http://www.10gen.com/presentations/mongosv-2011/schema-design-principles-and-practice
  • Just ask Gareth
  • Or use an arbiter Lose a datacenter spot just for the third replica (or arbiter)
  • Good support at the package level
  • Just be careful
  • One year with mongo db klmug presentation

    1. 1. One Year with MongoDB the Good, the Bad, the Ugly
    2. 2. Good: Schema-less
    3. 3. Bad: 2GB Database Limit on 32bit Machine
    4. 4. Ugly: Migrations
    5. 5. Ugly: Dates
    6. 6. Good: Query Language
    7. 7. Ugly: Management Tools and Interfaces
    8. 8. Good: Ruby ORM Support
    9. 9. Bad: Replication Suport at the Driver Level
    10. 10. Ugly: (non)Transaction Support
    11. 11. Ugly: Using a Document Store as a Relational Database
    12. 12. Ugly: Long Field Names
    13. 13. Bad: Background Indexing
    14. 14. Good: Replication It’s Easy™ It’s Easy™
    15. 15. Ugly: Replica Sets Need to be in Threes
    16. 16. Good: Very Fast to Setup
    17. 17. Bad: No Authentication by Default
    18. 18. It’s been a great year, and our team is looking for many more years of MongoDB goodness :) (actually we just want like the pizza)
    19. 19. @parasquidfacebook and twitterfacebook and twitter

    ×