DynamoDB to Postgres: Why and How
I submitted this article because of a single paragraph:<p>&gt; When it came to the different types of NoSQL databases, it was pretty clear that a document store best suited our needs. We needed to be able to query based on the data so key&#x2F;value was out, there was no need to have the ability to make all of the complex connections between data of a graph db, and nobody actually knows what a column db is (jk but our data is not the right use case for it). So document it was. We would have to change our data layout a bit to really work well with most document databases, our current data structure was similar to what you would expect for a relational db with tables etc since dynamo also uses a table structure. I wanted something that was ACID, none of that eventual consistency nonsense. That took a lot of them out of the race right there.<p>I don&#x27;t get it. He needed arbitrary querying, relations, ACID, tables. And yet... his first thought was to go to a document-based no-sql database and is only later hit with the sudden realization that his relational data is bet suited in a relational database.<p>What has gone so wrong here that an otherwise smart and educated engineer makes these kinds of fundamental mistakes? Is it the success of no-sql marketing departments, and the apparent un-sexiness of traditional relational databases? Is it education? The job market? A fear of SQL (that you never really have to write anyway...)? Is it the quick-fix non-relational databases give you?<p>As far as I can see there are very very very few nails that a PostgreSQL hammer cannot hit. I guess that&#x27;s part of the point of the article, but why does it need an article to explain this?<p>How can we stop these kinds of articles from <i>needing</i> to be written?<p>&gt; The change drastically increased the speed of our API, some requests are up to 6x faster than they were with Dynamo. The account details request, our previously slowest call, took around 12 seconds with Dynamo and was reduced to 2 seconds with Postgres!<p><i>sigh</i><p>Edit: Not sure why this has been moved to the bottom of the thread. I wasn&#x27;t trying to single this particular developer out, I was merely commenting on this troubling trend. Apologies if this came across in the wrong way.