It's 2026, Just Use Postgres (tigerdata.com)

Article summary

The article argues that using multiple specialized databases can lead to unnecessary complexity and costs, and that PostgreSQL can handle various workloads with the right extensions. It suggests that teams should start with one database and add complexity only when needed. The article also highlights the benefits of using PostgreSQL, including its ability to handle search, vectors, time-series, documents, caching, queues, and geospatial data. By using a single database, teams can simplify their infrastructure and reduce costs.

Main themes

• Database complexity
• PostgreSQL capabilities
• Specialized databases
• Infrastructure costs
• Scalability
• Data management

What commenters say

• Some commenters agree that PostgreSQL is a great choice for many use cases, but others argue that specialized databases like Redis have their own strengths and use cases.
• The use of Redis is defended as being more than just a cache, with its data structures and algorithmic complexity making it irreplaceable in certain scenarios.
• Others argue that simplicity and ease of use are important considerations, and that PostgreSQL or even SQLite may be a better choice for many applications.
• There is disagreement over the trade-offs between using a single database versus multiple specialized databases, with some arguing that the added complexity is worth it for specific use cases.
• Some commenters share their own experiences with PostgreSQL and other databases, highlighting the importance of considering specific needs and use cases when choosing a database.
• The idea that PostgreSQL can replace multiple specialized databases is seen as overly simplistic by some, who argue that each database has its own strengths and weaknesses.
• The importance of simplicity and ease of use is emphasized by some commenters, who argue that PostgreSQL or other databases may be a better choice for many applications due to their ease of setup and maintenance.