CouchDB: Lessons learned building a rails + iOS app

D02b5e0b9a348fa8d9bd2cac025eead3?s=47 Steven Ringo
February 14, 2012
140

CouchDB: Lessons learned building a rails + iOS app

Lessons learned using CouchDB to build a rails 3 app as a synchronised back-end for an iOS app running an embedded version of CouchDB.

D02b5e0b9a348fa8d9bd2cac025eead3?s=128

Steven Ringo

February 14, 2012
Tweet

Transcript

  1. Steven Ringo | steven@dynamicclarity.com | @stevenringo CouchDB Lessons learned building

    a rails + iOS app
  2. Why CouchDB?

  3. None
  4. None
  5. Online. Sometimes.

  6. Push updates.

  7. Multiple backends.

  8. BLOBs.

  9. No custom API.

  10. Syncing is hard.

  11. Universal datastore.

  12. Migrations.

  13. Availability of an mobile implementation.

  14. SQL is not NoSQL

  15. SQL != !SQL

  16. SQL = SQL? W A T ?

  17. None
  18. Forget everything you learned about SQL.

  19. Everything.

  20. EF Codd

  21. Normalization is not normal.

  22. MapReduce

  23. Futon

  24. MapReduce is scary. But not as scary as SQL (was)

  25. ORMs

  26. CouchCocoa for iOS

  27. Everything persists. Everything.

  28. couch_potato gem

  29. couchrest gem

  30. Bye-bye ActiveRecord. Hello ActiveModel

  31. Do not use couchrest_model

  32. Replication is trivial

  33. imagine git in a database context.

  34. MVCC. No locking. No mess.

  35. None