Well, Erlang has its own database that can store Erlang terms (see mnesia). As you can save some there for the impedance mismatch.
Nitrogen itself deals with reducing the differences between your backend code and the frontend. See the demos and their source code for examples: http://nitrogenproject.com/demos
Erlang also makes it a lot more easier to model stateful applications. I've found the best way to make an active web app with Erlang is just to make a regular application for the command-line (or the Erlang shell), and then add bindings to a web-server.
Because every block of code you have is independent, this is really easy to do. It makes every program extremely modular and I've rarely had the concept of 'code reuse' come so easily.
Maybe stackless python could be an interesting option under this perspective too, but I never used it for any project.
Nitrogen itself deals with reducing the differences between your backend code and the frontend. See the demos and their source code for examples: http://nitrogenproject.com/demos
Erlang also makes it a lot more easier to model stateful applications. I've found the best way to make an active web app with Erlang is just to make a regular application for the command-line (or the Erlang shell), and then add bindings to a web-server.
Because every block of code you have is independent, this is really easy to do. It makes every program extremely modular and I've rarely had the concept of 'code reuse' come so easily.
Maybe stackless python could be an interesting option under this perspective too, but I never used it for any project.