> Should You Use Postgres?

> Most of the time - yes. You should always default to Postgres until the constraints prove you wrong.

Interesting.

I've also been by my seniors that I should go with PostgreSQL by default unless I have a good justification not to.

If the only tool you know is a hammer, everything starts looking like a nail.

Discussion on the same topic "Postgres over Kafka" - https://news.ycombinator.com/item?id=44445841

I am excited about the Rails defaults where background and cache and sockets are all database driven. For normal-sized projects that still need those things, it's a huge win in simplicity.

I've found Kafka to be not particularly great with languages other than Java, if Confluent schemaregisty is involved.

I had fun working with the schema registy from TypeScript.

Isn't listen/notify absurdly slow and lock contentious

No-one ever regretted using a piece of infra to do what it wasn't planned for, during an incident at 3AM

Couldn't agree more. Have built and ran an in-house postgresql based queue for several years. It can handle 5-10k msg/s in our production workloads.

This is an article in desperate need for some data visualizations. I do not think it does an effective job of communicating differences in performance.

Just dropping this here casually:

  sup {
      position: relative;
      top: -0.4em;
      line-height: 0;
      vertical-align: baseline;
  }