![Add Data
// create some data
newPeople = []](https://image.slidesharecdn.com/nosqlandcoldfusion-111118225823-phpapp01/85/Using-NoSQL-MongoDB-with-ColdFusion-44-320.jpg)
![Add Data
// create some data
newPeople = []
arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘john@doe.com’})](https://image.slidesharecdn.com/nosqlandcoldfusion-111118225823-phpapp01/85/Using-NoSQL-MongoDB-with-ColdFusion-45-320.jpg)
![Add Data
// create some data
newPeople = []
arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘john@doe.com’})
arrayAppend(newPeople, {‘fname’: ‘Jane’, ‘lname’ : ‘Doe’})](https://image.slidesharecdn.com/nosqlandcoldfusion-111118225823-phpapp01/85/Using-NoSQL-MongoDB-with-ColdFusion-46-320.jpg)
![Add Data
// create some data
newPeople = []
arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘john@doe.com’})
arrayAppend(newPeople, {‘fname’: ‘Jane’, ‘lname’ : ‘Doe’})
// save everything at once
people.saveAll(newPeople)](https://image.slidesharecdn.com/nosqlandcoldfusion-111118225823-phpapp01/85/Using-NoSQL-MongoDB-with-ColdFusion-47-320.jpg)
![Find / Update
person = people.query().$eq("fname", "Jane").find()
// update a record
person[“email”] = “jane@doe.com”
person.update(person)](https://image.slidesharecdn.com/nosqlandcoldfusion-111118225823-phpapp01/85/Using-NoSQL-MongoDB-with-ColdFusion-50-320.jpg)
Ad
More Related Content
What's hot (20)
Viewers also liked (11)
Ad
Similar to Using NoSQL MongoDB with ColdFusion (20)
Ad
Recently uploaded (20)
Using NoSQL MongoDB with ColdFusion
- 1. NoSQL with ColdFusion Using MongoDB Indy Nagpal CFObjective, Melbourne, 2011
- 2. About me
- 3. About me ✴ Straker Translations, New Zealand ✴ Been working with CF for a while now ✴ Cloud-based applications using Railo ✴ Love CFWheels ✴ nagpals.com/blog, @indynagpal
- 4. NoSQL?
- 5. NoSQL? ✴ Different things to different people ✴ Non-Relational rather than NoSQL ✴ System for storage/retrieval of data ✴ Persistence layer is not a responsibility of a single system
- 6. Why NoSQL?
- 7. Why NoSQL? ✴ 100s of millions of items in a big table
- 8. Why NoSQL? ✴ 100s of millions of items in a big table ✴ Dynamic data structure
- 10. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 11. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 12. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 13. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 14. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 15. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 16. SQL NoSQL Static Data Structure Dynamic Data Structure Dynamic Query Static Query (generally) Consistency Eventual consistency Transactions Limited Transactions Difficult to distribute Distributed, fault-tolerant Limited performance under load Optimized for heavy read-write
- 17. NoSQL DBs
- 18. NoSQL DBs ✴ Used with CF ✴ Apache CouchDB ✴ MongoDB ✴ Amazon SimpleDB ✴ CF/Java Wrappers available
- 19. What is MongoDB
- 20. What is MongoDB ✴ A Document-oriented database ✴ “Humongous” ✴ Scalable, high-performance, open-source ✴ An alternative to relational databases ✴ One of the NoSQL technologies
- 21. Key Difference
- 22. Key Difference ✴ Most No-SQL databases ✴ dynamic data ✴ static queries ✴ MongoDB ✴ dynamic data ✴ dynamic and static queries
- 23. Basic Concepts
- 24. Basic Concepts ✴ Database
- 25. Basic Concepts ✴ Database ✴ Collections (broadly like table)
- 26. Basic Concepts ✴ Database ✴ Collections (broadly like table) ✴ Documents (like row)
- 27. Basic Concepts ✴ Database ✴ Collections (broadly like table) ✴ Documents (like row) ✴ Fields (like columns)
- 28. Basic Concepts ✴ Database ✴ Collections (broadly like table) ✴ Documents (like row) ✴ Fields (like columns) ✴ Collections are indexed
- 29. Basic Concepts ✴ Database ✴ Collections (broadly like table) ✴ Documents (like row) ✴ Fields (like columns) ✴ Collections are indexed ✴ Cursors (retrieve data as required)
- 30. Concepts
- 31. Concepts ✴ New terminology ✴ Similar ideas, but not identical ✴ RDBMS - columns defined for tables ✴ NoSQL - fields defined for documents ✴ Collections are more like containers
- 32. Drivers
- 33. Drivers ✴ Officially supported drivers ✴ Language-specific drivers (Java, Ruby, etc.) ✴ Framework-specific (MongoMapper) ✴ Wrappers built on top of drivers ✴ cfmongodb built on Java drivers ✴ Unlike Apache CouchDB that uses REST
- 34. BSON
- 35. BSON ✴ Binary JSON format ✴ Supports embedding of documents and arrays within other documents and arrays ✴ Lightweight ✴ Traversable ✴ Efficient ✴ bsonspec.org
- 36. CF and Mongo
- 37. CF and Mongo ✴ cfmongodb (on Github) -- excellent ✴ Wrapper around Java drivers ✴ Most functionality encapsulated ✴ Inserts, updates, delete, find ✴ Map-reduce, Geospatial
- 38. CF and BSON • Structs/arrays persisted as they are! people = mongo.getDBCollection(“people”) person = { “fname” : “John”, “lname” : “Doe” } people.save(person)
- 39. Init
- 40. Init mongoConfig = createObject( 'component', 'cfmongodb.core.MongoConfig').init(dbName="test")
- 41. Init mongoConfig = createObject( 'component', 'cfmongodb.core.MongoConfig').init(dbName="test") mongo = createObject('component', 'cfmongodb.core.Mongo').init(mongoConfig)
- 42. Init mongoConfig = createObject( 'component', 'cfmongodb.core.MongoConfig').init(dbName="test") mongo = createObject('component', 'cfmongodb.core.Mongo').init(mongoConfig) people = mongo.getDBCollection('people')
- 43. Add Data
- 44. Add Data // create some data newPeople = []
- 45. Add Data // create some data newPeople = [] arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘[email protected]’})
- 46. Add Data // create some data newPeople = [] arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘[email protected]’}) arrayAppend(newPeople, {‘fname’: ‘Jane’, ‘lname’ : ‘Doe’})
- 47. Add Data // create some data newPeople = [] arrayAppend(newPeople, {‘fname’: ‘John’, ‘email’ : ‘[email protected]’}) arrayAppend(newPeople, {‘fname’: ‘Jane’, ‘lname’ : ‘Doe’}) // save everything at once people.saveAll(newPeople)
- 48. Find / Update
- 49. Find / Update person = people.query().$eq("fname", "Jane").find()
- 50. Find / Update person = people.query().$eq("fname", "Jane").find() // update a record person[“email”] = “[email protected]” person.update(person)
- 51. Tools
- 52. Tools ✴ Terminal console ✴ MongoHub (Mac) ✴ MongoExplorer, MongoVision (Windows) ✴ SSH Tunnel to connect ✴ mongohq.com (hosted MongoDB/admin)
- 54. MongoDB and Railo ✴ Railo Extension ✴ Cache CF variables/data ✴ Store key-value pairs ✴ cacheGet() ✴ cachePut()
- 55. Queries and Map- reduce
- 56. Queries and Map- reduce ✴ Queries - rapid development ✴ Map-reduce - advanced querying ✴ Query and Map-reduce together give MongoDB an edge over other NoSQL alternatives
- 57. Data Modeling
- 58. Data Modeling ✴ No Joins! Scary? ✴ Embedding documents supported via ID ✴ Big mind shift ✴ ‘Fear’ of duplicate data drives design decisions in relational db world
- 59. CF ORM
- 60. CF ORM ✴ No support in CF ORM frameworks ✴ Other language frameworks more advanced ✴ Ruby on Rails - mongomapper ✴ Need ORM integration for wider adoption
- 61. Asynchronous
- 62. Asynchronous ✴ Asynchronous inserts/updates ✴ Journaled ✴ Capped Collections (FIFO)
- 63. Time taken to add 20,000 records with 5 words in each record 30 25 Time in Seconds 20 15 10 5 0 mysql (cfquery) filesystem (cflog) mongodb (cfmongodb)
- 65. Compelling features ✴ On-demand database and collection creation ✴ Asynchronous writes ✴ Replication - simple and easy ✴ Large-scale data processing ✴ Sharding - horizontal scaling ✴ Geospatial indexes
- 66. When to use?
- 67. When to use? ✴ Relational DBs suffice for most projects ✴ Abstraction via ORM is very useful ✴ MongoDB -- alternative/add-on ✴ Removes reliance on only one data storage mechanism
- 68. Learning Curve
- 69. Learning Curve ✴ Syntax ✴ Concepts like sharding, replication ✴ Well-documented / blogged ✴ Active mailing list ✴ Being used in production
- 70. So...
- 71. So... ✴ Another tool to have in one’s kit ✴ Extremely useful and easy to use ✴ Worth spending some time on
- 72. Thank you! @indynagpal [email protected] http://nagpals.com/blog
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: Two application problems:\n\nApplication 1: \n100s of millions of rows being written in clustered CF app\nSingle table with fixed number of columns\nMysql works, but slows down\nNo replication\n\nApplication 2\nApplication to generate mini applications, where number of columns can differ from each mini application to mini application\nBasic analytics needed\n\n
- #13: Two application problems:\n\nApplication 1: \n100s of millions of rows being written in clustered CF app\nSingle table with fixed number of columns\nMysql works, but slows down\nNo replication\n\nApplication 2\nApplication to generate mini applications, where number of columns can differ from each mini application to mini application\nBasic analytics needed\n\n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: \n
- #63: \n
- #64: \n
- #65: \n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n
- #71: \n
- #72: \n
- #73: \n
- #74: \n
- #75: \n
- #76: \n
- #77: \n
- #78: \n
- #79: \n
- #80: \n
- #81: \n
- #82: \n
- #83: \n
- #84: \n
- #85: \n
- #86: \n
- #87: \n
- #88: \n
- #89: \n
- #90: \n
- #91: \n
- #92: \n
- #93: \n
- #94: \n
- #95: \n
- #96: \n
- #97: \n
- #98: \n
- #99: \n
- #100: \n
- #101: \n
- #102: \n
- #103: \n
- #104: \n
- #105: \n
- #106: \n
- #107: \n
- #108: \n
- #109: \n
- #110: \n
- #111: \n
- #112: \n
- #113: \n
- #114: \n
- #115: \n
- #116: \n
- #117: \n
- #118: \n
- #119: \n