Offline first with Couchbase Mobile

Editor's Notes

• #2: [30:00]
• #3: [28:00]
• #4: [25:00]
• #5: [23:00]
• #6: [21:00]
• #7: [20:00]
• #8: [18:00]
• #9: [16:00] Couchbase Lite is a lightweight, embedded NoSQL database on your device. Couchbase Lite is based on the CouchDB replication protocol. I say that it is local first and implicit offline-support. By that, I mean that your code on the client will just be interacting with Couchbase Lite for CRUD-operations. Will show some code later which lets you connect to the Sync Gateway and start synchronizing.
• #10: [15:00] Sync Gateway handles all replication, access control and filtering of documents that are synchronized to the client devices. This makes it perhaps the most important part of this setup, and where most of the configuration happens. I’ll go into more details about how this is done in the next few slides.
• #11: [14:00]
• #12: [13:00] Channels are logical groupings of documents, and provide read access to users or user groups. Sync function: Considers access privileges, business logic and the actual content. When synchronizing, Couchbase Lite can request select channels, or retrieve all the channels available to the user.
• #13: [12:00] So, Couchbase will not try to merge changes, and instead provides a really simple, but perhaps stupid, algorithm for deciding which revision to use. Selecting a «winner» is not always a good option. In that case, you need to take over. Basically, you can check a document to see if it has conflicting revisions, and then your business logic must either choose which revision to keep or how to merge them. You should really clear up the conflicting revisions even if your app can accept the choice Couchbase makes for you, as the conflicting revisions will stay in the database and take up space until deleted.
• #14: [11:00]
• #15: [10:00]
• #16: [08:00]
• #17: [07:00]
• #18: [06:00]
• #19: [05:00]
• #20: [04:45]
• #21: [03:45]
• #22: [02:45]
• #23: [02:00]
• #24: [01:30]
• #25: [01:00]