website VS ybdemo

As engineers, we all know the feeling of encountering a stubborn bug that defies easy resolution. The Gitpod team recently faced such a challenge when we discovered a bug with our Gitpod Docs Search functionality during a comprehensive documentation restructure. The search feature was not updating correctly, returning outdated data even after we manually ran an Algolia indexing query to update the production data with newly deployed changes. This left us scratching our heads, wondering how to resolve the issue and ensure that our users could access the most up-to-date information quickly and easily.

This is a small doc from a PR I submitted to Gitpod's how-to guides but the prefer to have only a few databases in this guide (PostgreSQL, MySQL, Redis, MongoDB). No problem, I'll post this doc here.

Here is their repository on GitHub: https://github.com/gitpod-io/website

As I did with Oracle, I can run a single insert and look at the statistics from explain analyze and my ybwr:

I've also updated my YugabyteDB Lab with Grafana for this scenario, running:

I check, with my ybwr.sql script, that reading one row from the job_fanout view reads from one table only:

Here is a quick test using my ybwr on this demo table which has 3 tablets across 3 nodes.

If you want to play with a multi-node, as you need multiple network interfaces, it is better not to use this image but start YugabyteDB nodes in docker, as I do in my ybdemo:

@franckpachot

I've used this docker-compose

I'm starting a RF=3 cluster on my laptop using my ybdemo/docker/yb-lab/ and I set two aliases, ysqlsh, for SQL commands, and yb-admin, for snapshot commands:

I also load my ybwr.sql to show the number of rocksdb seek() and next() in the tservers:

Now that you know how to scale out, just with the --join option of yugabyted, you can build your docker-compose file. For example, to replace PostgreSQL in a Docker Compose used for tests, I use the same variables as the PostgreSQL image - example here. And yugabyted is convenient for quick start, but you can have more control by starting all components like I do when I demo high availability and elasticity: https://github.com/FranckPachot/ybdemo/tree/main/docker/yb-lab