When you’re about to start a project and are trying to make a decision on the what applications to use, one way to proceed is to find out what other people have to say about the available options, especially from others with first-hand experience with those available options.
That’s the most prudent way.
The other way, of course, is to go through the options and have your own experience. But that can be costly, both in terms of time and money.
That’s why I linking to an article by Nick Manning, the developer of Shindig, a mobile app for those who love to drink and share what they’re drinking with others who also love to drink and also love to share what they’re drinking with others who…
His article is about how he went from using Postgres to MongoDB, then finally to Neo4j. Postgres (or PostgreSQL) is a relational database, while MongoDB and Neo4j are NoSQL databases. MongoDB is, of course, the most popular NoSQL database, while Neo4j is the most popular NoSQL graph database. All three database applications are Free Software.
So why did Nick switch from an SQL database to a NoSQL database? And why did he later switch from that NoSQL database to another NoSQL database? If you’re a developer trying to decide what database to use for a project, reading Nick’s article, which is titled Switching From MongoDB to Neo4j, is a good place to start.
Here’s an excerpt from his article:
I think investing time in learning how to really leverage a graph database is a major asset for any full stack engineer. It’s easy to use for simple projects and if your project grows, it can cope with complexity and perform well.
You may read the rest here.