mORMot Open Source

GuruRamana

Member

Registered: 2014-08-21

Posts: 2

any stat comparison between mORMot and WebAPI Restful service?

I was wondering if anyone has any performance stats available between mORMot and WebAPI Restful service. The client is looking at implementing a restful service and am just trying to find a better solution. mORMot sounds wonderful so far, and was looking for any info on how well it performs against asp.net WebAPI X.0.

Thanks.

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,224

Website

Re: any stat comparison between mORMot and WebAPI Restful service?

You could take a look at http://robertocschneiders.wordpress.com … ts-part-2/
There was WCF and mORMot in the landscape of this benchmark.

Note that this benchmark is very limited: it tests only a "hello world" transmission from the server.

From my own experiment, mORMot tends to use less memory than WCF/WebAPI, being faster, is easier to configure (no .exe.config nightmare), and has its ORM layer available, especially for authentication or simple RESTful access to any remote database.
For instance, mORMot has JSON integration from the ground up, so is much more aggressive than the .Net solutions. And it does not suffer from Garbage Collection lags: a mORMot server can run for days, with very little memory, serving thousands of clients, in production. See http://synopse.info/forum/viewtopic.php?pid=9989#p9989

Besides performance, the main interest of our framework is that you have the full source code of the mORMot framework at hand, so you are not tied to use the WebAPI as a black box. For instance, we were not able to create stand-alone WCF services implementing CORS (which is IMHO mandatory for AJAX clients) - you need to host the server in IIS.
We were areadly stuck with unnotified change of default security policy of WCF, on the Microsoft side, when the customer did make a regular Windows update, and upgraded its .Net stack from 4.0 to 4.5.x. Similar unexpected breaking changes may also appear with WebAPI, since it is part of the system. The mORMot approach is stand-alone, so you won't suffer from it.

Furthermore, installing a mORMot server is just a matter of copying one executable, without any runtime to install.
The same for the clients.

But of course, WCF/WebAPI are best for pure C# clients, since you would have the whole client and server stack on the same framework.

Of course, don't take my word for all this, since I designed the mORMot, but it is my own experiment when creating DDD complex solutions in both WCF and mORMot.