Realm is awesome! I have been using it for a year now in a large production iOS/swift app with great success.

Great job on the recent additions to the more fine grain notifications, with this I was recently able to reduce my own code, simplify and increase performance!

Core data is good and a powerful weapon, and certainly educational to learn its approach and how to use it effectively. I sometimes ponder if going through the that first has made me a more competent iOS developer.

Realm is the right tool for the job for me in most use cases. Don't see myself switching back anytime soon, keep up the good work!

Congrats to the team for expanding their platform support. I'm still interested to see what sync looks like.

If you are interested in mobile databases, you'd do well to evaluate Cocuhbase Mobile, which is 100% open source, available for most mobile platforms, and includes bulletproof synchronization with its open source secure cloud server.

More info here http://developer.couchbase.com/mobile/

Can someone elaborate how this differs from JPA/Hibernate style ORMs ?

The examples look suspiciously similar.

EDIT: So i easily believe that it's nicer than CoreData, and I see that there is lots of potential to reduce an ORMs complexity by assuming a single Writer (Process of App), but the core Problem seems to be exactly the same. - And the solution looks also very familiar. -> Proxy Objects, Bytecode manipulation to intercept field access etc.

Does it handle the uncool cases of ORMs better? - Unloading of state when thousands/millions of objects are touched once

- Collection fetching of large collections, iterators/chunks

- OrderedList O(N) index update for non-append inserts

- What happens to invalidated (deleted) objects? are collections updated live?

- Does is handle cascades explicitly/implicitly/not ?

I'm quite interested in this, since it may solve real pain problems.

Realm has excellent marketing, but being a closed source third party SDK disqualifies it as anything I would recommend for my company to use.

I've had to deal with enough pain from closed source libraries from the likes of Google and others. Closed-source prevents me from adopting a new platform until the vendor gets around to porting it, and only if it fits with their strategy. Also a middleware-only company is liable to be bought out, and then closed. Example: Parse.

What exactly is Realm's business model? The core is closed-source, but as far as I can tell, it's free for application developers to use.

Congrats on 1.0!

+1 for not just telling us what Realm is, but for showing us (with inline code), and for supporting React Native :)

What about using realm Java outside of Android? The readme says:

> This repository holds the source code for the Java version of Realm, which currently runs only on Android.

I'm interested in trying this on the desktop (windows/linux/mac), but that doesn't seem possible? Wonder what makes it android only.

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

Congrats on the release, glad you made it to 1.0. And well done sticking to semantic versioning and going to 0.100 before doing the 1.0.

Yes. I've been using Realm for my work app. In my opinion it's easier than Core Data, and certainly much easier than bare SQLite.

I've expected it to cross 1.0 after 0.99 but it keeps going on to more than 0.101. So, congrats on finishing the milestone.

One request though: what about grouping functionality?

Please don't say it is faster than SQLite anymore. http://kpgalligan.tumblr.com/post/133281929963/my-talk-at-dr...

my main frustration with realm is that the design for the rxjava support is not that great. I can't use custom schedulers when fetching data and almost always end up mapping realm data objects to Pojo immutable entities generated with Autovalue, thus giving up the lazy loading speedup (since I have to copy all the data). also sometimes the asObservable() method returns empty collections a few times before returning the whole collection EVEN IF FILTERED WITH .isLoaded() and is wayyy too much spammy (it redelivers to subscribers a whole lot more times than when the underlying model is written to), therefore I have to debounce the stream with 1 second to save the adapter from rebinding the whole dataset again.

Been using Realm in all of my Android projects for the last 8+ months. It has now become my defacto mobile database for all my mobile projects. It's that easy to use. Gets out of the way and lets me focus on business problems, not bit shifting problems.

Just curious, why is there no Realm support for web & mobile web using localstorage? It seems like that could be useful, to re-use your model/data tier between react native and a react web app.

As I understand it Realm is an Object database. It's similar to the GemStone Smalltalk database in that regard but only local to the device.

How does Realm tackle data syncing between devices ?

undefined

Does Realm support NSFetchedResultsController-like functionality ?

I'm currently starting work on an iOS application which will display large lists of data which will be constantly updated on a background thread...

I wonder how Realm implements lazy-loading / faulting of off-screen items .. ?

undefined

So, not a whole lot is known durability. Any pointers?

https://www.google.com/search?q=site%3Arealm.io%20durability...

If you're into React Native, check out Realm. Great experience for me so far.

I'm using Realm for my React Native project it awesome! Thanks Realm team.

Well I read the front page of the website which says that Realm is a replacement for sqlite and coredata.

I didn't gain any understanding though of why they needed to be replaced and how Realm is different.

Is having to use the Realm objects in the same thread they were created it much of a burden on how you use it? Having not tried it yet I wondered about that limitation.

Really wish there was a C interface to tinker with.

Realm's team, congrats for the good work.

I use Realm for React Native and it's awesome! Congrats to the Realm Team. great work!

Awesome! Congrats to Realm and their entire team!

Will we see some NativeScript support?

for react native, how does realm compare to relay?

undefined

The "What is Realm?" paragraph begins with "Realm is not an ORM".

Jesus Christ, that was the very first line.

In order to use this, you have to have know SQLite, given that, why would I spend time to learn something that wraps around it?

Most of the time you do a insert/update/view, something that a simple helper class would do well.