The rx Java Examples shows how Realm works together with Rx Java.
The unit Test Example shows how you can write unit tests when working with Realm.
If you want to check whether your Realm instance has auto-refresh activated or not, use the on a class without a primary key, an exception will be thrown.
When you use primary keys, reads (queries) will be slightly faster, but writes (creating and updating objects) will be a little slower.
Creating an in-memory Realm with the same name as a persisted Realm isn’t allowed—names still have to be unique.
When all in-memory Realm instances with a particular name go out of scope with no references, that frees all that Realm’s data.
While your application continues working with a synchronized Realm as if it’s a local file, the data in that Realm might be updated by any device with write access to that Realm.
In practice, your application works with any Realm, local or synchronized, the same way, although opening a synchronized Realm requires a User that’s been authenticated to the Object Server and that’s authorized to open that Realm.
Take a look at our examples to see Realm used in practice in an app.
Realm Studio is our premiere developer tool, built so you can easily manage the Realm Database and Realm Platform.
With Realm Studio, you can open and edit local and synced Realms, and administer any Realm Object Server instance. You can use the standalone Realm Browser Mac application to read and edit Generate demo database. You can also use the Stetho-Realm plugin for Stetho, an Android debug bridge for the Chrome browser created by Facebook.
The multi Process Example shows how to use Realm from different processes in the same APK.
Before you can use Realm in your app, you must initialize it. A synchronized Realm uses the Realm Object Server to transparently synchronize its contents with other devices.
To keep an in-memory Realm “alive” throughout your app’s execution, hold onto a reference to it. This has a lot of benefits with regards to type safety.