Throughout the year, Opa adopted a JavaScript-like syntax, gained support for MongoDB and now Node.js.Opa positions itself as the enterprise JavaScript framework due to the safety and security provided by its strong static typing system.

Indeed, Opa checks the type safety of the application over the whole application, from client, to server, to database. Opa also provides many automation algorithms, such as the automated use of Node.js fibers at runtime, automated client/server and server/database dialog.

Sorry, I am probably the one to blame with the 'ORM' keyword;)
Turns out, I've been telling for years that I don't like them, as they add yet another layer in the technology soup.
But the duo Opa + MongoDB is way different. It's a very thin layer of technology at runtime to build web applications. And I guess neither are very easy to implement.
There may have been similar solutions at the mainframe era, but the advantages of those two is that they are built on the "modern" standards and in the end allow to build applications that run in the modern browsers.

phy_si_kal writes: The new, open source, Opa web programming language just hit version 0.9.0 "S4", six month after its last major release.Apart from a new syntax more similar to JavaScript, the new releases focuses on mongoDB integration.Opa now features something similar to ORM except that mongoDB is a non-relational, document-oriented database and Opa a functional, non-object-oriented language.The new functionality makes the NoSQL database even easier to use as all language-database calls are automated. And the mapping of functional datastructures to documents could even be much better than current ORM approaches and solve the object-relational impedance mismatch.Link to Original Source

We have many comments about the license and we listen, and we thank you for them.
We listen, and will engage a discussion with our community soon to see how we could make things better.
However, please note that you don't have to make your code "public domain". Of course, you retain the full copyright to your code -- what we currently ask is that you make the code of the application available to your users.

Indeed, there's no such thing as the database passwd in Opa. The database is only accessed by a single application, which logics controls the access. For instance, your application code allows to create one admin user, who can choose a passwd which is stored in the database. Then, this user has the credentials to change all things when other users don't.
And of course, the database content is not covered by the AGPL license.