This past week I had the privilege of presenting at and attending RailsConf 2022 Conference in Portland, OR. My presentation was titled Puny to Powerful PostgreSQL Rails Apps. This post will focus mainly on my presentation experience.
Recently I had the opportunity to travel to NYC to present at PGConf NYC 2021.
In the StaffEng book, there is a section called Work on What Matters.
Finding duplicate rows following an application bug can be tricky to do in a performant way. One way to improve the speed and simplicity of identifying the duplicate rows is doing both the find and delete all in SQL, as...
By using unlogged tables we can insert rows at a higher rate compared with a normal table. But there is a trade-off.
Over time our indexes became bloated, meaning invisible rows were still present in the index. This is inefficient and can be addressed by rebuilding the index.
This tip is a recipe for how to recover from a Rails migration that failed to apply in production, by applying it manually. This process could work for any SQL migration but the example used below is for an index...
We operate a high scale API application that relies on a single primary PostgreSQL instance. We have scaled up the DB instance vertically, acquiring more CPU, Memory, and disk IO over time.
Indexes on tables are great for finding a needle (or a few needles) in a haystack.
Authentication and authorization with JSON technologies can be a confusing mess of of acronyms, so this post is an attempt to sort these out. This post including the title, is very similar to Red Thunder: JWTs? JWKs? ‘kid’s? ‘x5t’s? Oh...