🚀I am excited to reveal Nile to the world finally!. Nile is serverless Postgres database for modern SaaS. Nile virtualizes tenants into the database to provide. 1. Tenant isolation and per-tenant backups.2. Drop-in organization and user management.3.

The single metric I have optimized for in my career was the quality of people I work with. You want to surround yourself with really smart people and be greedy to learn as much as possible from them. Promotions, money, responsibility was a consequence of optimizing for that one.

If you are a startup and your application is slow, your OLTP DB performance is not the problem 99.9% of the time. Perceived latency your user might see : 600-800ms for page load.DB query latency : 5-10ms. Focus on the right problem to optimize.

RT @gwenshap: Sharding sounds like a simple way to scale a database. It is very effective - but there are still ways to do it wrong. For….

This is really sad, if true.

With systems engineering, there are no shortcuts to learning. You have to grind it out for years by building and operating systems of different kinds. The theory is useful but the learning on the job is invaluable.

Thoughts on building highly available systems. A bit long and a brain dump of things I have learnt over multiple decades of building large-scale databases and storage systems. At massive scale (10,000+ nodes), you will have failures all the time. Correlated failures are even.

Some folks were interested to know why. - Calling MCP from Cursor on your local dev box and reading customer data is an anti pattern . Customer data should not leave out of production.- Need more secure OSS MCP server examples that are officially blessed. MCP authors largely just.

You should not use MCP against your production database!. MCP is useful during development l/testing and it ends there.

RT @ligantoine02: +1 for @niledatabase for native multitenant support in #postgresql.

Reliability is 40% system design and 60% operational excellence . Operational excellence is really hard since it involves process and cultural change. We went through this at Confluent and was painful. Much easier to create the culture of operational rigor when the team is small.

There are different reasons/benefits with every OLTP DB architecture. I would classify them into largely three types and I have run and managed all three versions in my lifetime. Pick your option based on what your company needs. 1. Full local storage. This is kind of how we ran.

Somehow we have accepted the out of order of news feed timeline as perfectly normal way to consume news content.

RT @PostgresFM: New episode: "Multi-tenant options". Nikolay and Michael are joined by @gwenshap to discuss multi-tenant architectures — th….

RT @gwenshap: Built an AI travel buddy on my day off! 🤖 . Told it: “Plan a fun day in California wine country.” Got an epic itinerary! . W….

RT @gwenshap: Learning Postgres: from “SELECT ” to "reading the source code for fun". Here’s my favorite list of resources to level up yo….

RT @gwenshap: You think 'SELECT 1;' is simple? . Let’s walk through everything that happens just to return the number 1 from an existing….

RT @gwenshap: “Why is Postgres seq-scanning rather than use this index?” 🤯. Short answer: the planner thinks that index won’t help (or can’….

RT @gwenshap: Biggest mistake you've ever made in production? . Mine is from 25 years ago: . My manager asked me to "clean space on the da….

RT @gwenshap: Troubleshooting auth is the one of the hardest problems in software engineering. Modern auth flows involve 3-4 different ser….