swift-composable-architecture VS GRDB.swift

One point that's not being discussed enough -- using SwiftUI (since it's heavily value-typed / struct-based) prevents a whole host of problems around retain cycles, typically the bugbear of iOS dev. I recently built an iOS app from scratch with recent grads with zero Swift experience (but had done React).

It was ~2mo before they even had to learn what a retain cycle was, and that was from using UIKit.

Of course you still eventually see this if / when you use `@ObservedObjects` and their implementation, but in our case we were also using https://github.com/pointfreeco/swift-composable-architecture which hides this away as well.

There’s a nice open source swift library by the pointfree guys, called The Composable Architecture (TCA). Check it out 🙂

It looks like you reinvented the Reducer pattern, have you had a look at Composable Architecture?

[Books by Objc.io](https://www.objc.io/books/) are great. Also whilst not a book, [Composable Architecture](https://github.com/pointfreeco/swift-composable-architecture) seems like a nice way to develop cross platform (iOS/macOS) apps.

Regarding MVVM, since your list is very SwiftUI-forward (which is great) I’m surprised that the Composable Architecture pattern was not mentioned. (https://github.com/pointfreeco/swift-composable-architecture)

I use a variation on The Binder Architecture. Another one I like a lot and that works well with SwiftUI is The Composable Architecture.

Check out pointfree’s composable architecture series GitHub repository

The Composable Architecture is a must-have. It provides the most complete and battle-hardened architecture - check out the examples in the repo, or check out their videos on it called A tour of The Composable Architecture, which should give you a good overview of what it looks like and its benefits.

Do take a look at https://github.com/pointfreeco/swift-composable-architecture and their videos though

Give a try? Why not? Maybe you will like this as well: https://github.com/pointfreeco/swift-composable-architecture

Instead of either of these options, I would highly recommend checking out GRDB instead. It's a very nice SQLite wrapper that helps you avoid many of the concurrency issues affecting both Core Data and Realm: https://github.com/groue/GRDB.swift

Its performances are indeed not bad: https://github.com/groue/GRDB.swift/wiki/Performance. One could say that Realm performances are exaggerated in their marketing materials, and that SQLite is unmatched, and by far.

GRDB - A toolkit for SQLite databases, with a focus on application development. Language: Swift.

Library author here - SQLite concurrency needs a little care: don't miss the Concurrency Guide: https://github.com/groue/GRDB.swift/blob/master/Documentatio...

All async apis are 🔥 EXPERIMENTAL. You can help them become stable: provide feedback.

Instead I would read the database with a 3rd party library like SQLite Swift or GRDB.

These are impressive! The use of screenshots and figures really helps. I've also always thought Groue's GRDB is an example of great documentation and readme combination[1].

[1] https://github.com/groue/GRDB.swift

I certainly remember how it was at the time GRDB did not support associations 😅. The lib has turned very capable since then: https://github.com/groue/GRDB.swift/blob/master/Documentation/AssociationsBasics.md

Your choices aren't just Realm or Core Data - your might be better served by SQLite instead, using something like GRDB.swift