A Postgres table, carefully protected behind a thick undergrowth of privileges and policies. Photo by ZACHARY PEARSON on Unsplash

User Types, defined as roles


Newly launched Lambdas flying into an unreserved concurrency pool. Photo by Nick Fewings on Unsplash

Infrastructure as Code


An unprepared candidate sitting down to an interview with me. Photo by Caleb Woods on Unsplash

Solve problems multiple times, slowly, and vocally


An aerial view of Google’s Git repository. Photo by Dan Meyers on Unsplash


Two software engineers playing outside after they saved countless hours by going server-less with GraphQL. Photo by Jenn Evelyn-Ann on Unsplash
  1. The application has users
  2. Users can create things
  3. Access to things


Elephants standing performantly between some trees. Photo by Jeff Lemond on Unsplash

But why?


Automate all of the things! Source: https://www.flickr.com/photos/56682936@N03/15572646535

Bottlenecks


Austin, circa 2015

Food


Application Users as PostgreSQL Roles

An Experiment Giving Database Roles to Application Users


This is actual utilization data from a Volta station at Macy’s Pasadena Plaza on Lake Avenue

Caleb Brewer

I build things by breaking them.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store