Scaling for one. If 95% of your workload is non-transactional reads, why introduce transactions? If your writes are single table and don't require transactiona

Scaling for one. If 95% of your workload is non-transactional reads, why introduce transactions? If your writes are single table and don't require transactional safety, why introduce transactions? If you need complex, multiple-insert or update writes, transactions are great, but that can also be accomplished in a stored proc. In a high-velocity environment, avoiding transactions are a great way to get more throughput out of your database server with lower latencies. Combine Postgres with pgBouncer in statement mode and you can scale it pretty dramatically.