The best of both Relational and Document DB paradigms
March 21, 2017
The best of both Relational and Document DB paradigms
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with PostgreSQL
We use PostgreSQL across the organization for data storage across multiple web-based microservices. It's easily scalable, hosted on AWS, and provides deeper features we need when querying against complex data types (namely against JSON).
- Native JSON support
- Intuitive command line integration
- Easy Docker hosting
- Shared extensions. We use the pgcrypto extension (for UUID support) and frequently install it to the wrong schema by mistake. Extensions are difficult to move, and this is an easy mistake to make.
- Clearer delineation between "databases" and "schemas" would help to better understand the system.
- PostgreSQL has allowed us to spin up multiple web services for client support very quickly, completely negating the time required to start working on a new project or with a new client - the effective "zero bottleneck" of PostgreSQL setup means we can focus more on actual sales rather than onboarding.
- Amazon DynamoDB and MySQL
PostgreSQL provides both the traditional relational DB setup of MySQL and a more document-driven model like that of DynamoDB. As some of our data is relational and some is document-based, it was more efficient to select the tool that did both than run two, separate databases. PostgreSQL offers all of the features we need.