Hands on Realm Database for Android projects
In one of the Android app projects at Oursky, we started using Realm for data caching. So users won’t have to look at blank pages when they log back to the app, waiting for remote API results.
We think it’s a minimalistic yet reliable solution, and is worth giving it a shot for your next app. Just beware of the differences between versions, follow the conventions, and pay extra attention when using with other libraries.
More is discussed below in details and with example snippets.
What is Realm?
Realm is the mobile database solution that proposed as a replacement for SQLite & Core Data.
It’s like using SQLite with an ORM (as those who used SQLAlchemy may have experience), with a lot of awesome and convenient methods for data transactions.
However, Realm is NOT built on top of SQLite. It persists on its own persistence engine.
Realm is also cross-platform that supports both iOS and Android, so developers who write Java, Swift, Objective-C can share the same Realm files painlessly.
Getting Started
To get Realm for your Android project, you can use either Maven or add a Jar into the project.
For more, see the official installation guide
So, is it cool?
Realm is said to be lightweight and fast compared to traditional solutions, like using SQLite and a fully-fledged ORM.
Bundling Realm into your app saves space and is capable of doing pretty much the same thing.
IMHO, the simplicity and minimalistic nature of Realm is its biggest advantage, but also its limitation over other solutions at the same time.
This is how we define a Post record for Realm:
Realm realm=Realm.getInstance(this.getContext());
realm.beginTransaction();
Post post =realm.createObject(Post.class);
post.setTitle(“Awesome Topic Title”);
post.setBody(“Main body passage we write along”);realm.commitTransaction();
Query the first Post:
post =realm.where(Post.class).findFirst();
On the bright side, being fast and light-weighted is a huge advantage when it comes to building mobile applications.
The transaction on Realm is really fast. Also, using a light-weight SQLite + ORM alternative also means that your app will be slightly smaller, which might appeal to some users.
On the other hand, as a highly integrated tool, flexibility is sacrificed. Using Realm means that you will have to follow its strictly pre-defined methods and procedures.
For a traditional SQLite + ORM setup, if there is a case where the ORM of your choice cannot cater to, you can always write your own standard SQL code. This is something almost, if not entirely, impossible to do with Realm.
Some limitations
However, (till May 2015) there are serval limitations you might want to consider before using :
Getter and Setter Restrictions
Due to how the proxy classes override getters and setters in the model classes, there are some restrictions to what is allowed in a model class:
public class Person extends RealmObject{
private String name;
private int age;public String getName(){ return name;
}public void set Name(String name){ this.name=name;
}public int getAge(){ return age;
}public void setAge(int age){ this.age=age;
｝｝
- Only private instance fields
- Only default getter and setter methods
- Static fields, both public and private
- Static methods
- Implementing interfaces with no methods
So you can not extend anything else than RealmObject or to override methods like toString() or equals().
Not supporting null values
You can not store null as a value for primitive data types (booleans, integers, floating-point numbers, dates, and strings). You will need an extra boolean field to capture if a field is null or not.
and further more listed here.
Originally published at code.oursky.com on May 5, 2015.
Building an app? Our free developer tools and open source backend will make your job easier.
