Postgresql

A while back, when I was just starting to get more hands-on with AWS and infrastructure, I ran into a performance issue that took me longer than I’d like to admit to figure out. At the time, we were upgrading one of our Rails applications to a newer version. Instead of upgrading the existing EC2 instance, we decided to provision a new one and deploy the application there. It felt like the safer approach since we could leave the old server untouched until we were confident everything was working as expected. ...

I was working on a Rails application that used two PostgreSQL databases. The primary database was owned by our application, so we could create it, run migrations, and modify the schema whenever we needed to. The second database was different. It belonged to another application, and our application only connected to it for reading data. We didn’t own its schema, and we weren’t responsible for running migrations against it. Everything worked perfectly on my local machine, so I didn’t think much about it. ...