SimplePGDBA

TL;DR: I managed to create a 6 node cluster and run a distributed database on it. Got me a nice Playground, and some interesting things to investigate. Background: Serverless, but I want multiple nodes (mostly kidding: because there is always a server running somewhere) But, like some of my friends say: Serverless is The Future.  As a database-person; I've now started to explore a distributed database. And bcse I already knew approx how to use docker-containers as "little severs", that was a logical way to start. I also had already experimented with yugabyte both in docker (1 node, 1 container,  following these examples) and on the free cloud-offering ( cloud.yugabyte.com ). But those were all still "single node". I could do postgres-commands (nice, all of my scripts + demos worked...), but RF=1 is not really what Yugabyte is designed for. I needed more nodes... Creating and Running multiple nodes. Luckily, there was this example by Franck: https://dev.to/yugab...

TL;DR: Use SQL to expose information. And use Catalog and similar info to do it. Some pro/con arguments, and some Examples below. Note: I'm not tweeting or otherwise promoting this blog. It is just info for those who have the link or can search cleverly.  I'm using this post to send a few notes to some  friends, who may or may not use the info further.  Aim: Find + Expose data via SQL To create some "catalog" information (views) about my Yugabyte objects. My overall-aim: use SQL to find info related to the catalog, and to the back-end. Ideally, I get to use SQL and  combine  the info.  Yugabyte exposes some of this at ports 7000 (tserver) and 9000 (master) Background :  Yugabyte stores data in Tablets , which are stored at Nodes in clusters. A Tablet is replicated over multiple nodes (3 nodes if the RF=3: Replication Factor). The "Front-end" of Yugabyte, the part that the Developer sees, is using the Postgres code, hence YB is a perfect fit-in if you ...