FMDB VS Swinject

There’s a number of indie devs who rely on https://github.com/ccgus/fmdb for fast persistence. The rebirth of NetNewsWire came with FMDB at it’s core (https://inessential.com/2020/05/18/why_netnewswire_is_fast)

In a project I‘ve adopted, this package is used alongside CoreData to access SQLite features which aren’t possible in CoreData. I would recommend it, it‘s pretty old but has SPM support. But it’s written in Obj-C, maybe this is off-putting for you, so you may find something similar but written in swift.

FMDB - A Cocoa / Objective-C wrapper around SQLite. Language: Objective-C.

DI is a concept which makes a class independent of its dependency management. It achieves that by decoupling the usage of an object from its creation. This helps you to follow SOLID’s dependency inversion and single responsibility principles. To achieve this in Swift one of the most appreciated library is Swinject. This library not only provides DI but also have many other features like:-

Swinject - Dependency injection framework for Swift. Language: Swift.

We use Swinject which is probably quite similar https://github.com/Swinject/Swinject

So, how do we fix this? There is a cleaner solution. By using a dependency injection framework, such as Swinject we can create a base module that we might call the DI module.