https://medium.com/@dcordero/data-sources-in-swift-or-how-to-avoid-that-this-new-trendy-persistency-framework-determines-the-5472fcb75eda
Data Sources in Swift… or how to avoid that this new trendy persistence framework determines the architecture of your App
There are really good frameworks to deal with the persistency of our data in the world of iOS.
Core Data for instance is a great solution offered by Apple that provides an incredible good performance even when dealing with a really huge amount of data. But there are also, some other alternatives poping around. One of these alternatives is Realm which is said to offer even better performance than Core Data, with a simpler syntax.
But sadly, not eveything is as wonderful as expected in this world of persistency. There are also plenty of problems. I have had really bad experiences with Core Data, Realm or many of these other trendy persistence frameworks out there, of course not only because of the frameworks itself, but because of how they are applied to the projects.
The main problem is that, due to the complexity of the problem that these frameworks solve, they tend to have a quite complex syntax. And if the scope of the framework is not clearly defined, their objects in the end tend to be scattered all around the project, finding UIViews taking data from NSManagedObjects, UICollectionViews populating cells using RLMObjects, etc…