PostgreSQL for Everything
The author advocates for the use of PostgreSQL as a versatile, all-in-one database solution for various technical projects. Drawing on personal experience, the article highlights its SQL standard compliance, full-text search capabilities, and extensibility as reasons to prefer it over more fragmented database architectures.
Why it matters
It provides a professional perspective on database architecture, emphasizing simplicity and efficiency in software engineering.
Contrary to popular belief - the answer to everything is NOT 42 - it's PostgreSQL. (ok. It might also be Postgres ).
I started using PostgreSQL roughly in 2003 for a research project called ColumbaDB . Columba is no more, but PostgreSQL is still alive and kicking more than ever.
In 2003, MySQL was much more widely used than PostgreSQL. MySQL was also potentially faster as it did not implement all features of the SQL standard. At the same time MySQL was lacking many features that we needed (full-text search, powerful indexes, SQL standard compliance etc). PostgreSQL felt more like a "real" database in comparison to MySQL - like a tiny version of Oracle - but in open source clothes.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in