3 ms·
I'm the creator of Opa. When we released Opa in June 2011, it had only a native backend. Most of the feedback we got was to support a standard runtime, which we
by hbbio 14y ago
I'm the creator of Opa.
When we released Opa in June 2011, it had only a native backend. Most of the feedback we got was to support a standard runtime, which we did when we chose to target Node.js as we already generated JavaScript client code.
Why (now Opa supports HTML5 and the like) do you think native backend is better?
- greyfade 14y agoPersonally, Node.js+MongoDB is counter to my intended use cases. NoSQL databases are incompatible with my data models. Node.js has limitations in responsiveness, especially for complex (read: data/code-heavy) responses. It simply doesn't meet my needs, and the community's focus is on improving areas that are completely orthogonal to my needs. A native backend that is properly threaded and uses, e.g., continuations and thread pools to manage highly concurrent requests is far more preferable compared to Node.js, and proper support for RDBMS and memcached meets my needs better than MongoDB could ever dare dream.