 This can lead to clearer source code than the paired codice_2 / codice_3 syntax of SQL, and so avoids its problem of unclosed transactions within a procedure.Again as a result of the functional nature of Erlang, nesting transactions is simple.It's also possible to distribute transactions across multiple nodes (i.e.