The Holy Grail of Persistence?
One of the very first CTO-grade decision I had to take in the making of Snoget was to pick what would become our main transactional persistence engine. Since we’re using Erlang exclusively for our production servers, the solution seemed easy: use Mnesia. But I settled for PostgreSQL.
At this point, anyone who’s been dealing with O/R mapping (like Ted Neward who said: “Object/relational mapping is the Vietnam of Computer Science”), should cry fool: Mnesia would offer me persistence without any impedence mismatch with the application runtime environment and I preferred a SQL database to it? Actually, to someone who has used an O/R mapper before and who switched to Erlang, discovering Mnesia for the first time is a sheer heavenly moment similar to that:
Check also related entries: