FFeroz Shah1h ago · 8 min readCatching schema drift before it breaks productionMigrations only describe a database as long as nobody changes it any other way. Then someone adds a column during an incident, a DBA widens a type, a data import relaxes a constraint, and nobody writefsmutimeer.hashnode.dev
FFeroz Shah1h ago · 10 min readStop using ddl-auto=update in productionspring.jpa.hibernate.ddl-auto=update is the fastest way to get started: change an entity, restart, and the table follows. It stays in the configuration long after the first demo, and one day it runs afsmutimeer.hashnode.dev
SSaaSClerk4h ago · 4 min readYour billing inbox is an append-only log. Your database probably is not.Every spend-management tool begins the same way: it reads receipts out of an inbox. The mail server keeps those messages. Then we copy what we parse into rows we are free to rewrite, and that is wheresaasclerk.hashnode.dev
MMuhammad Ali Mughal7h ago · 9 min readSaaS Backup & Disaster Recovery: RPO, RTO and PITRA nightly pg_dump to the same VPS is not a backup strategy. It is a file that disappears with the disk, the compromised root account or the provider incident that took the server down in the first plaresume-ai.hashnode.dev
ZZyVOP10h ago · 11 min readChoosing a Vector Database: pgvector vs Dedicated StoresThe real question isn't which vector database is best. It's where your vectors should live: next to the rest of your data in Postgres, or in a system built only for similarity search. Many teams alreablog.zyvop.com
AAnthony Emmanuella Mmasinachi11h ago · 12 min readAgata Proxima: PostgreSQL Security, Tenant Isolation & Database Access VerificationIntroducing Agata Proxima: PostgreSQL Security, Tenant Isolation & Data Protection A new security platform for SaaS companies, developers, and organizations that need stronger control over how their Phttpsagataproximacom.hashnode.dev
AAbolfazl Mohajeri20h ago · 14 min readHow Does PostgreSQL Decide How to Execute a Query?When you send a SQL query to a database, have you ever wondered what actually happens behind the scenes? Consider the following query: SELECT * FROM orders WHERE user_id = 123 ORDER BY created_at DESCblog.abolfazlmohajeri.ir
SSubramanya M Rao18h ago · 20 min readBuilding Reliable LinkedIn and Instagram Feeds with NestJS, PostgreSQL, and Azure BlobThe first requirement was to show our company's LinkedIn posts inside an employee portal. We already collected public posts and displayed them in a feed. Then we noticed that some cards had no image. subramanyarao.hashnode.dev
MMadhav Bhasin1d ago · 6 min readCloud SQL vs AlloyDB vs Firestore: Picking the Right Database on GCPThe question engineers actually ask isn't "what are the trade-offs between Cloud SQL, AlloyDB, and Firestore?" It's: "I'm building a new service — should I use Firestore or Cloud SQL?" The honest answblog.madhav.dev
ZZyVOP1d ago · 10 min readPostgres Performance Basics: Reading EXPLAIN Output and Fixing Slow QueriesA slow query is a guess until you see its plan. Postgres will tell you exactly how it intends to run a query and, with one extra keyword, how the run actually went. Learning to read that output is oneblog.zyvop.com
