Story time! The very first version of Bugbot we launched was stateless. We kept track of runs in our analytics database and we only used that data offline for metrics. Whenever we needed to analyze run metadata, we had to do online lookups from the database. Relying on our analytics database during online operations was definitely tech debt. We were using a large RDS cluster that was already running hot from offline usage. We started noticing that some Bugbot runs were failing because of external analytics load; by that time, we had added a few Bugbot-specific tables to it, so we had to come up with a migration plan quickly before this became a widespread availability issue. We chose PlanetScale Postgres for our new Bugbot cluster. We already had many terabytes of data in PlanetScale MySQL/Vitess which was working incredibly well, so we felt comfortable with this choice. The migration went very smoothly, and now all of Bugbot's queries are instant and we stopped worrying about downtime!