PostgreSQL logo

PostgreSQL

A powerful, open source object-relational database system
63.2K
50.6K
+ 1
3.5K

What is PostgreSQL?

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
PostgreSQL is a tool in the Databases category of a tech stack.
PostgreSQL is an open source tool with 9K GitHub stars and 3K GitHub forks. Here’s a link to PostgreSQL's open source repository on GitHub

Who uses PostgreSQL?

Companies
5273 companies reportedly use PostgreSQL in their tech stacks, including Uber, Netflix, and Instagram.

Developers
56203 developers on StackShare have stated that they use PostgreSQL.

PostgreSQL Integrations

Datadog, Slick, Amazon DynamoDB, JSON, and Sequelize are some of the popular tools that integrate with PostgreSQL. Here's a list of all 295 tools that integrate with PostgreSQL.
Pros of PostgreSQL
754
Relational database
507
High availability
436
Enterprise class database
380
Sql
302
Sql + nosql
171
Great community
145
Easy to setup
129
Heroku
128
Secure by default
111
Postgis
48
Supports Key-Value
46
Great JSON support
32
Cross platform
29
Extensible
26
Replication
24
Triggers
22
Rollback
21
Multiversion concurrency control
20
Open source
17
Heroku Add-on
14
Stable, Simple and Good Performance
13
Powerful
12
Lets be serious, what other SQL DB would you go for?
9
Good documentation
7
Intelligent optimizer
7
Scalable
6
Transactional DDL
6
Modern
6
Reliable
5
Free
5
One stop solution for all things sql no matter the os
4
Relational database with MVCC
3
Full-Text Search
3
Developer friendly
3
Faster Development
2
Excellent source code
2
search
2
Great DB for Transactional system or Application
1
Text
1
Full-text
1
Free version
1
Open-source
Decisions about PostgreSQL

Here are some stack decisions, common use cases and reviews by companies and developers who chose PostgreSQL in their tech stack.

Shared insights
on
PostgreSQL

PostgreSQL is responsible for nearly all data storage, validation and integrity. We leverage constraints, functions and custom extensions to ensure we have only one source of truth for our data access rules and that those rules live as close to the data as possible. Call us crazy, but ORMs only lead to ruin and despair. PostgreSQL

See more
Emanuel Evans
Senior Architect at Rainforest QA · | 15 upvotes · 670.1K views

We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

Read the blog post to go more in depth.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 11 upvotes · 268.2K views

We primarily use MariaDB but use PostgreSQL as a part of GitLab , Sentry and Nextcloud , which (initially) forced us to use it anyways. While this isn't much of a decision – because we didn't have one (ha ha) – we learned to love the perks and advantages of PostgreSQL anyways. PostgreSQL's extension system makes it even more flexible than a lot of the other SQL-based DBs (that only offer stored procedures) and the additional JOIN options, the enhanced role management and the different authentication options came in really handy, when doing manual maintenance on the databases.

See more
Jelena Dedovic

Investigating Tortoise ORM and GINO ORM...

I need to introduce some async ORM with the current stack: Tornado with asyncio loop, AIOHTTP, with PostgreSQL and MSSQL. This project revolves heavily around realtime and due to the realtime requirements, blocking during database access is not acceptable.

Considering that these ORMs are both young projects, I wondered if anybody had some experience with similar stack and these async ORMs?

See more
Martin Johannesson
Senior Software Developer at IT Minds · | 12 upvotes · 310.6K views

At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

See more

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more

Blog Posts

Dec 8 2020 at 5:50PM

DigitalOcean

+11
2
1809
Nov 20 2019 at 3:38AM

OneSignal

+8
8
3892
Jul 9 2019 at 7:22PM

Blue Medora

+8
11
1781

Jobs that mention PostgreSQL as a desired skillset

See all jobs

PostgreSQL Alternatives & Comparisons

What are some alternatives to PostgreSQL?
MySQL
The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
MariaDB
Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
Oracle
Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
MongoDB
MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
SQLite
SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.
See all alternatives

PostgreSQL's Followers
50567 developers follow PostgreSQL to keep up with related blogs and decisions.