The article examines the role of Postgres in pub/sub messaging and queuing, emphasizing a shift in the tech industry towards simpler, more pragmatic solutions. The author contrasts two camps: one that chases trends without critical evaluation and another that favors common sense and effective resource use. The emergence of the "Small Data" movement and the resurgence of Postgres indicate a growing recognition that complex systems like Kafka may not be necessary for many use cases. Benchmark results highlight Postgres's performance in pub/sub and queue scenarios. In a pub/sub setup with a single c7i.24xlarge instance, Postgres achieved a throughput of 238 MiB/s and 1.2 million messages per second with a latency of 853 ms. For queuing, it delivered 19.7 MiB/s and over 20,000 messages per second, though latency was higher due to bottlenecks. The author notes that while Postgres isn't a direct substitute for specialized systems like Kafka, it can effectively handle more than 80% of use cases with significantly less complexity. The distinction between queues and pub/sub systems is crucial. Queues are designed for one-to-one communication and do not guarantee message order, while pub/sub systems enable one-to-many communication with strict ordering expectations. The author developed a custom workflow for implementing pub/sub in Postgres, mimicking Kafka's log structure. This approach sheds light on the potential of Postgres beyond traditional database roles, especially for those seeking a less complex alternative to established messaging systems.