Realm VS CoreStore

Presumably realm in Element for Android. https://realm.io/ "Realm by MongoDB"

See also https://github.com/vector-im/element-android/issues/1025

Looks really cool, I like to make very minimalistic dependency choices for the web apps I work on. Web Components look interesting and it's great to see frameworks that build upon it and provide features that are currently missing from it.

When I landed on the page I remembered another Realm framework I used a lot long time ago. https://realm.io has the same name and the logo looks very similar too. Not sure if it's a problem, just wanted to share. :)

Realm (Open Source but Sync is SaaS)

Realm is a fast, scalable alternative to SQLite with mobile to cloud data sync that makes building real-time, reactive mobile apps easy.

I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.

So yeah, if you don't have a server with API which will store data for you - you should really look into CoreData and Realm

Try Realm.

Just to add to this, there's also Realm and ObjectBox as alternatives.

There is some crossover between the BaaS of Firebase and what MongoDB Atlas is offering if you are developing using Atlas Sync and Realm. Even so, there is a whole lot more you can find in terms of tutorials and community support for Firebase so it is hard to know how many of the Mongo claims are just future bugs for your project vs what people are currently doing with Firebase.

It’s not from Apple, but there’s a framework called CoreStore which you might find easier to pick up initially.

Core Data (and CoreStore, which is backed by Core Data) is an object persistence system (so objects can survive between application sessions), which lets you work with the objects in a more database-like way. For example, you can ask for all the instances of a Person object which match a predicate like the pets relationship is not nil. You can think of it like a more advanced version of arrays and sets.

If you’re just starting out with Core Data, you may want to take a look at CoreStore. It’s an external dependency, but it does feel much more at home in Swift. Less of the constant optional unwrapping, for one.

CoreStore (though iCloud support is still in the works)

More complicated than that is Core Data. It’s extremely powerful, but pretty weird to use at first. Doesn’t feel very Swift-y (Check out CoreStore for a more Swift feel). This is great for hundreds or thousands of objects. You can retrieve objects which match a particular search predicate, objects can have relationships to one another (e.g, a manager object can have an employees relationship to multiple employee objects), which you can traverse a lot like normal objects-which-contain-objects. This is massive overkill for storing strings, but great for something like a Twitter or Reddit client.

All the issues in the article had been solved by CoreStore since Swift’s inception. Check it out

CoreStore works really well for pure Swift models: https://github.com/JohnEstropia/CoreStore/blob/develop/Playground_iOS.playground/Contents.swift

CoreData through CoreStore. Full disclosure: I’m the author of the lib

Source: I am the author of the CoreStore library. The faulting behavior of NSManagedObjects are what makes them incompatible with redux-type architecture (ex: SwiftUI) which is why CoreStore exposes an ObjectSnapshot as a struct wrapper layer for live objects.