If this is representative of your database:
CREATE TABLE tasks (
id BIGINT GENERATED ALWAYS AS IDENTITY,
created_at TIMESTAMPTZ DEFAULT CURRENT_TIMESTAMP,
args JSONB,
PRIMARY KEY (id)
);
Is this how developers view a database in 2025? A place to store a JSON blob?
Its trade offs.
If you already have Postgres in place for other use-cases, using it for this purpose is a completely valid trade-off.
If transactionality is important, it’s a valid trade off.
If I don’t need what other data store would give me (perf, HA writes), why would I bother setting up and operating a completely separate system.
And even for non relational use cases, Postgres is still a better option in many cases
This is perfectly reasonable if you need document features in some tables. I would strongly prefer this over something like Mongo DB.
Your example demonstrates how little of PostgreSQL syntax you actually know.