IBM DB2 vs PostgreSQL: What are the differences?
What is IBM DB2? A family of database server products developed by IBM. DB2 for Linux, UNIX, and Windows is optimized to deliver industry-leading performance across multiple workloads, while lowering administration, storage, development, and server costs.
What is PostgreSQL? 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.
IBM DB2 and PostgreSQL belong to "Databases" category of the tech stack.
"Rock solid and very scalable" is the top reason why over 5 developers like IBM DB2, while over 744 developers mention "Relational database" as the leading cause for choosing PostgreSQL.
PostgreSQL is an open source tool with 5.38K GitHub stars and 1.79K GitHub forks. Here's a link to PostgreSQL's open source repository on GitHub.
reddit, Instacart, and StackShare are some of the popular companies that use PostgreSQL, whereas IBM DB2 is used by XMLi5 Ltd., ITAIPU BINACIONAL, and Applic8. PostgreSQL has a broader approval, being mentioned in 2701 company stacks & 2097 developers stacks; compared to IBM DB2, which is listed in 7 company stacks and 9 developer stacks.
What is IBM DB2?
What is PostgreSQL?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using IBM DB2?
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
In my opinion PostgreSQL is totally over MongoDB - not only works with structured data & SQL & strict types, but also has excellent support for unstructured data as separate data type (you can store arbitrary JSONs - and they may be also queryable, depending on one of format's you may choose). Both writes & reads are much faster, then in Mongo. So you can get best on Document NoSQL & SQL in single database..
Formal downside of PostgreSQL is clustering scalability. There's not simple way to build distributed a cluster. However, two points:
1) You will need much more time before you need to actually scale due to PG's efficiency. And if you follow database-per-service pattern, maybe you won't need ever, cause dealing few billion records on single machine is an option for PG.
2) When you need to - you do it in a way you need, including as a part of app's logic (e.g. sharding by key, or PG-based clustering solution with strict model), scalability will be very transparent, much more obvious than Mongo's "cluster just works (but then fails)" replication.
We decided to use MemCachier as our Memcached provider because we were seeing some serious PostgreSQL performance issues with query-heavy pages on the site. We use MemCachier for all Rails caching and pretty aggressively too for the logged out experience (fully cached pages for the most part). We really need to move to Amazon ElastiCache as soon as possible so we can stop paying so much. The only reason we're not moving is because there are some restrictions on the network side due to our main app being hosted on Heroku.