In this diagram, the pink Realm block represents your Realm file from where your view controllers would read data. To understand why Realm’s write transactions are rock solid, let’s have a look at how they work.
Realm ensures as little friction as possible when you are writing to your data storage. Let’s have a look at the way that Realm’s write transactions make your app more resilient. Since your view controller doesn’t know anything about your networking or data controllers, in the case network is down, or unreachable, that doesn’t affect viewing and browsing data in any way.
The network and data controllers in the app work in the background and add new objects to your Realm while your view controllers operate on the main thread, and are only concerned about reacting to Realm notifications and refreshing the UI. In the previous episode, we looked at a small sample project called Inboxly, and you’ve seen how easy it is to separate concerns in your app. A couple of examples we are going to look into are keeping your app as functional as possible without network connection, and the way that Realm ensures you stay on your happy pad as you read or write objects on disk.
In this episode, we are going to have a quick look at how Realm allows you to make your apps more resilient. In this series, we’ve been looking at how Realm facilitates designing and developing reactive apps. As we’ve seen in previous episodes, reactive code exhibits a number of characteristics, regardless of whether you are using an actual reactive code framework, or features built into the iOS SDK. Hi, and welcome back to Building Reactive Apps with Realm.
0 kommentar(er)
