# How to Collapse Your Stack Using PostgreSQL for Everything - Timescale Blog Synced: [[2024_05_22]] 6:14 PM Last Highlighted: [[2024_05_21]] Tags: [[Career Growth]] [[Explainer]] [[Software]] ![rw-book-cover](https://www.timescale.com/blog/content/images/2024/05/How-to-collapse-your-stack-using-postgres-for-everything-1.png) Summary: Using PostgreSQL for everything can simplify your tech stack by reducing complexity and operational overhead associated with managing multiple databases. PostgreSQL's versatility and maturity make it a strong choice for handling various types of workloads, allowing you to focus on building features rather than managing different databases. Consider collapsing your stack with PostgreSQL to streamline your data flow and save time in the long run. ## Highlights [[2024_05_21]] [View Highlight](https://read.readwise.io/read/01hyefyfeq9m3e8ex833e3qa69) > Unless you're in the business of building databases, it’s usually unwise to develop your own; it's complex, risky, and requires a very specialized skill set. So, you might end up adopting various existing databases: Postgres for transactional data, Elastic for full-text search, Influx for time series, Pinecone for vector operations, and maybe ClickHouse for analytics. Suddenly, your tech stack is sprawling. [[2024_05_21]] [View Highlight](https://read.readwise.io/read/01hyefyx5r8jhjf4hpgwnqys01) > Each new database you add brings its own set of challenges: different languages to learn, consistency models to understand, and operational nuances that can’t be ignored. Not only does this add complexity, but it also introduces what I call “dotted line” complexity, the additional overhead that comes from each pair of systems which data flows between. The more databases and the more dotted lines you have, the harder it is to reason about the state of your system as a whole. > You’ve got more databases, and because of that, you’ve got more problems.