It depends on your situation: how many developers in your team, how much of an annoyance using pure SQLite is to the team, how often you need to touch the database, what’s your current architecture, etc. While I can’t say what’s best for you, I can share how it was better for us: 6 developers and counting, finding extremely annoying to have to deal with Cupboard (learning curve, basic documentation), pointing out the lack of reactiveness for our future architecture. It seemed a no-brainer.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store