You can write your stored procedures in a number of scripting languages. Out of the box PostgreSQL supports Tcl [1], Perl [2] and Python [3]. There's also a gen

You can write your stored procedures in a number of scripting languages. Out of the box PostgreSQL supports Tcl [1], Perl [2] and Python [3]. There's also a general mechanism to register other languages [4]. On github I found [5], which is embeds Ruby in PostgreSQL. I haven't used it and don't know how mature it is. Using the same scripting language in your stored procedures and application code might lessen the impedance mismatch. It doesn't solve testing, deployment/migrations and tooling. [1] https://www.postgresql.org/docs/current/static/pltcl.html https://www.postgresql.org/docs/current/static/pltcl.html [2] https://www.postgresql.org/docs/current/static/plperl.html https://www.postgresql.org/docs/current/static/plperl.html [3] https://www.postgresql.org/docs/current/static/plpython.html https://www.postgresql.org/docs/current/static/plpython.html [4] https://www.postgresql.org/docs/9.6/static/plhandler.html https://www.postgresql.org/docs/9.6/static/plhandler.html [5] https://github.com/knu/postgresql-plruby https://github.com/knu/postgresql-plruby