PostgreSQL vs Stack Overflow: What are the differences?
Developers describe PostgreSQL as "A powerful, open source object-relational database system". 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. On the other hand, Stack Overflow is detailed as "Question and answer site for professional and enthusiast programmers". Stack Overflow is a question and answer site for professional and enthusiast programmers. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about programming.
PostgreSQL can be classified as a tool in the "Databases" category, while Stack Overflow is grouped under "Question and Answer Sites".
"Relational database", "High availability " and "Enterprise class database" are the key factors why developers consider PostgreSQL; whereas "Scary smart community", "Knows all" and "Voting system" are the primary reasons why Stack Overflow is favored.
PostgreSQL is an open source tool with 5.44K GitHub stars and 1.8K GitHub forks. Here's a link to PostgreSQL's open source repository on GitHub.
Uber Technologies, Spotify, and Netflix are some of the popular companies that use PostgreSQL, whereas Stack Overflow is used by CircleCI, Intuit, and OpenGov. PostgreSQL has a broader approval, being mentioned in 2741 company stacks & 2176 developers stacks; compared to Stack Overflow, which is listed in 768 company stacks and 1637 developer stacks.
What is PostgreSQL?
What is Stack Overflow?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Stack Overflow?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use postgresql for the merge between sql/nosql. A lot of our data is unstructured JSON, or JSON that is currently in flux due to some MVP/interation processes that are going on. PostgreSQL gives the capability to do this.
At the moment PostgreSQL on amazon is only at 9.5 which is one minor version down from support for document fragment updates which is something that we are waiting for. However, that may be some ways away.
Other than that, we are using PostgreSQL as our main SQL store as a replacement for all the MSSQL databases that we have. Not only does it have great support through RDS (small ops team), but it also has some great ways for us to migrate off RDS to managed EC2 instances down the line if we need to.
PostgreSQL combines the best aspects of traditional SQL databases such as reliability, consistent performance, transactions, querying power, etc. with the flexibility of schemaless noSQL systems that are all the rage these days. Through the powerful JSON column types and indexes, you can now have your cake and eat it too! PostgreSQL may seem a bit arcane and old fashioned at first, but the developers have clearly shown that they understand databases and the storage trends better than almost anyone else. It definitely deserves to be part of everyone's toolbox; when you find yourself needing rock solid performance, operational simplicity and reliability, reach for PostgresQL.
Let's be honest here guys...the internet, technology, software, and most likely the lights wouldn't be on without Stack Overflow.
We are avid consumers of Q&A on Stack Overflow and other communities on the Stack Exchange network, and definitely wish to extend a heavy thanks to all the help is has provided over several lifetimes of various developers' and engineers' careers. We all try to answer questions, upvote, and comment when we have some knowledge to share, and aren't afraid to ask a question ourselves from time to time (and neither should you!).
Relational data stores solve a lot of problems reasonably well. Postgres has some data types that are really handy such as spatial, json, and a plethora of useful dates and integers. It has good availability of indexing solutions, and is well-supported for both custom modifications as well as hosting options (I like Amazon's Postgres for RDS). I use HoneySQL for Clojure as a composable AST that translates reliably to SQL. I typically use JDBC on Clojure, usually via org.clojure/java.jdbc.
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.
Tried MongoDB - early euphoria - later dread. Tried MySQL - not bad at all. Found PostgreSQL - will never go back. So much support for this it should be your first choice. Simple local (free) installation, and one-click setup in Heroku - lots of options in terms of pricing/performance combinations.
StackOverflow darf natürlich auf dieser Liste nicht fehlen. Die riesige Community konnte uns bereits bei verschiedenen Problemen zur Hand gehen, die wir nicht lösen konnten. Auf viele Fragen findet man hier eine Antwort und ohne StackOverflow, würde dem Entwicklerdarsein wohl etwas fehlen.
Stack overflow HAD to be included in this list. We can't count the endless hours stack overflow and its huge community has already saved us and will potentially save us in the future. Stack Overflow is the proof that nearly every problem one may experience, another one has already solved.
The go to source for PrometheanTV technical staff when they have a technical question or need help from the broader development community.