Event Handling in the Realm Object Server

Presented at the Realm meetup on December 8, 2016, this presentation serves as an introduction to the new event handling features of the Realm Mobile Platform.

Transcript

1. Event Handling in the Realm Object Server Realm Meetup - December 2016 Tim Oliver to@realm.io
2. @TimOliverAU to@realm.io • Cocoa Engineer at Realm • With the company since March 2015 • Main focus on utility and demo apps • From Perth in Western Australia • Former remote worker from Perth
3. Overview to@realm.io • Quick revisit of the Realm Mobile Platform • Introducing the concept of Event Handling • Demonstrating Event Handling
4. The Realm Mobile Platform name@realm.io
5. to@realm.io
6. name@realm.io A Data Ubiquitous World
7. name@realm.io “I deleted the app and when I reinstalled it, all of my saved items were gone! How do I get them back!?!” - Former Customer
8. Data synchronization isn’t automatic, and it isn’t easy. name@realm.io
9. name@realm.io Native object JSON Backend object SQL Backend object JSON Native object SQLite/CoreData SQLite/CoreData The Traditional Way
11. name@realm.io The Realm Way Native Realm Object Realm Object Server
12. af@realm.i Server-side Realms Device-side Realms Realm Object Server Real-time Sync The Realm Object Server
13. Reduces complexity by keeping data format consistent name@realm.io
14. Event Handling name@realm.io
15. RMP Developer Edition to@realm.io • Performs data synchronization between devices and server • It’s not possible to access user data on the server • Useful for maintaining consistent state across user devices • Not so useful for server-side processing / web services • (User devices could be used for processing/controlling events)
16. Pro/Enterprise Editions to@realm.io • Exposes read-write access to the user data on the server • Includes a special version of the Realm Node.js package • Can register callbacks for detecting when Realm data changes • Uses callbacks to respond to user-driven events • Third party services can then write data automatically
17. af@realm.i Push object changes server-side
18. to@realm.io Handling user-driven events var SERVER_URL = 'realm://127.0.0.1:9080'; var NOTIFIER_PATH = ‘.*/myrealm’; var admin_user = Realm.Sync.User.adminUser(REALM_ADMIN_TOKEN); var change_notification_callback = function(change_event) { console.log(‘A change occurred!’); }; Realm.Sync.addListener(SERVER_URL, admin_user, NOTIFIER_PATH, ‘change', change_notification_callback);
19. to@realm.io Handling user-driven events
20. to@realm.io Event-Handling Summary • Handled via Node.js to allow full Realm read-write access • Data can be shared with other backend services (eg MySQL) • Callbacks can be registered to respond to Realm data changes • All writes made from Node.js SDK automatically sync to devices
21. name@realm.io Demonstrating Event Handling © Clockready, Wikimedia Commons
22. to@realm.io The TextScanner App • Take a photo of some text. • Save that photo data to Realm. • ROS receives data, forwards it to Google OCR via a JSON REST API. • Receives REST response from Google, decodes and saves results back to Realm. • Resulting scanned text is synchronized to device and displayed on screen.
23. to@realm.io
24. to@realm.io The “Scanner” App • Take a photo of some text. • Save that photo data to Realm. • ROS receives data, forwards it to three Watson Image Recognition APIs • Asynchronously receives results from each API, and saves to same Realm object. • Changes to the Realm object are consolidated and sent back to app.
25. name@realm.io Demo!
26. We’re hiring to@realm.io • iOS Evangelist • Android Evangelist • C++ Core • Javascript • Automation Engineer • C# Engineer • Product Manager • and much more! realm.io/jobs
27. to@realm.io Questions? Tim Oliver to@realm.io www.realm.io @TimOliverAU