Data Based JavaScript

Transcript

1. Data Based JavaScript
2. DataBase JavaScript?
4. Heavily Inspired by Backbone.js ! • Documentation • API • Philosophy • Conventions
8. The Big Idea??
9. JavaScript “Holy Grail”
13. JavaScript “Holy Grail”
15. …but I’ve given talks on this before
16. …and there’s still a lot of work to be done
17. Data Based JavaScript
18. Backbone Models & Collections
20. Some Thoughts, Opinions
21. Some Thoughts, Opinions Backbone Models & Collections do too much
22. Some Thoughts, Opinions Backbone Models & Collections do too much Backbone Models & Collections alone aren’t enough
23. Some Thoughts, Opinions Backbone Models & Collections do too much Backbone Models & Collections alone aren’t enough There’s better ways than listening to individual change events
24. Some Thoughts, Opinions Backbone Models & Collections do too much Backbone Models & Collections alone aren’t enough There’s better ways than listening to individual change events
25. Backbone Models & Collections do too much
26. Backbone Models & Collections (might) do too much
27. Backbone Models & Collections (might) do too much Wrapping Data (attributes, get, set) Validations Change Notification Relations??? Syncing?? App Specific Logic Models
28. Backbone Models & Collections (might) do too much Wrapping Data (attributes, get, set) Validations Change Notification Relations??? Syncing?? App Specific Logic Wrapping models Adding, removing, fetching models Tight ties with model (change / url) Maybe pagination??? Maybe nested models?? Maybe…whatever else you want to put there? Models Collections
29. What should they do Wrapping Data (attributes, get, set) Return external relations based on attributes Limited Change Notification App Specific Logic Filter models Models Collections
30. Collections
32. .length .pop .push .shift .unshift .slice Array-like API
35. Behave like sorted maps
36. Behave like sorted maps which gets a little tricky…
37. { add: true remove: false merge: true } Collection#set
38. Backbone.Model and Backbone.Collection might not be enough
39. Backbone.Model and Backbone.Collection might not be enough Multiple “sources of truth”
40. Backbone.Model and Backbone.Collection might not be enough Multiple “sources of truth” Object Identity issues
41. Backbone.Model and Backbone.Collection might not be enough Multiple “sources of truth” Object Identity issues No definitive place of knowing what data exists in your application
42. Better than change events?
43. What might an elegant solution look like?
44. Limit scope of Models & Collections
45. Complexities of Models & Collections
46. Simplify of listening to change / time
47. Backbone.Session
48. Backbone.Session Think like a session cookie
49. Backbone.Session Think like a session cookie Similar to Backbone.sync
50. Backbone.Session Think like a session cookie Similar to Backbone.sync Models & collections reference back to session
51. getPath()
52. getPath()
55. Relations
56. model.set('first_name', 'Tim')
57. model.set('first_name', 'Tim') model.session.setIn(['users', 1, 'first_name'], 'Tim')
58. model.set('first_name', 'Tim') model.session.setIn(['users', 1, 'first_name'], 'Tim') refresh views containing models looking at paths ['users'], ['users', 1]
59. model.set('first_name', 'Tim') model.session.setIn(['users', 1, 'first_name'], 'Tim') refresh views containing models looking at paths ['users'], ['users', 1] Socket, Ajax, etc.
60. What does this gain us? Drastically simplifies Collections Single source of truth for everything data related Easy to switch into offline mode
64. Beyond Backbone Models & Collections
66. var x = new Immutable.Map({a: 1}); ! var y = x.set('b', 2); ! x.get('a') // 1 ! y.get('a') // 1 ! x.get('b') // undefined ! y.get('b') // 2
67. Takeaway Points If you like Node but want RDBMS check out Knex & Bookshelf
68. Takeaway Points If you like Node but want RDBMS check out Knex & Bookshelf Maybe Backbone.Session could be a thing?
69. Takeaway Points If you like Node but want RDBMS check out Knex & Bookshelf Maybe Backbone.Session could be a thing? Or maybe &.Session?
70. Summary Time spent critically analyzing the data flow in your application can save a lot of time later