Trendoday

Using atomic transactions in Postgres to power an idempotent API

2 comments · api, databases

  • Comments2
–Rank now
#16Peak rank
1Days on list
–Score · 7d
Oct 31, 2026First seen

On Lobsters

apidatabases
Score
24
Comments
2
Submitted by
brandur
Tags
api, databases
Site
brandur.org

Story details from Lobsters ↗ · linked article on brandur.org.

Trending history

Using atomic transactions in Postgres to power an idempotent API was first seen on Lobsters · Hottest on Oct 31, 2026. Since then it has appeared in 1 check on 1 different day. Its best position was #16 of 25, reached on Oct 31, 05:21 UTC. It dropped off the list after Oct 31, 05:21 UTC.

Rank history

Position on Lobsters · Hottest at every check (lower is better).

#1#9#17#25 04:5105:0605:2105:3605:51 Oct 31, 05:21 UTC · #16

Last 14 days

Best rank per day (UTC).

Oct 26today

From the discussion

A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.

> Using atomic transactions in Postgres to power an idempotent API Haha. I hadn't even noticed that I'd written it that way, but I guess that's how I've internalized it. I just pushed a fix that'll be visible as soon as the page expires out of CloudFront.

Questions

Is Using atomic transactions in Postgres to power an idempotent API trending on Lobsters right now?

Not at the moment. It was last on the list on Oct 31, 05:21 UTC, after 1 day of trending.

What is the highest rank Using atomic transactions in Postgres to power an idempotent API reached?

#16 on Lobsters · Hottest, on Oct 31, 05:21 UTC. Trendoday checks this list every 30 minutes.

How long has Using atomic transactions in Postgres to power an idempotent API been trending?

It was first seen on Oct 31, 2026 and has been on the list on 1 day (1 check) since.