For PostgreSQL-based applications, I think the licensing side is worth understanding alongside the technical details. PostgreSQL is especially interesting because its permissive license gives developers considerable freedom to use and modify the database. The same flexibility is useful when building infrastructure around PostgreSQL, particularly for projects that need reliable background processing. I’ve also been looking at tools that use PostgreSQL as the foundation rather than introducing another primary datastore. One example is https://spooled.cloud/, which uses PostgreSQL for durable job storage while keeping workers responsible for the actual application logic. That approach makes sense for teams that already rely heavily on PostgreSQL and want background jobs to remain closely connected to their existing data infrastructure.