Then again, so's Perl. The joys of implementation differences.
I find Nancy a lot easier to develop with than ASP.net. You do pay for the expressiveness however.
At work I'm deploying a Nancy based project to parse/process documents into structured data using a 3rd party vendor's SOAP service. There were some unpleasant compatibility issues with the SOAP service and our Perl server's SOAP client and zero logging so I took the service's source code (so glad the Vendor provided it) and replaced the WebService portion of it with a thin Nancy controller to route the calls and return JSON. Since most of the processing time is spent chewing on the files Nancy's overhead isn't an issue and Nancy made it dead simple to code.
For a compiled platform, nancy seems pretty slow http://www.techempower.com/benchmarks/
http://www.techempower.com/benchmarks/#section=data-r8&hw=i7...
But not much behind ASP.net.
http://www.techempower.com/benchmarks/#section=data-r8&hw=i7...
And quite a bit ahead of Sinatra
http://www.techempower.com/benchmarks/#section=data-r8&hw=i7...
Then again, so's Perl. The joys of implementation differences.
I find Nancy a lot easier to develop with than ASP.net. You do pay for the expressiveness however.
At work I'm deploying a Nancy based project to parse/process documents into structured data using a 3rd party vendor's SOAP service. There were some unpleasant compatibility issues with the SOAP service and our Perl server's SOAP client and zero logging so I took the service's source code (so glad the Vendor provided it) and replaced the WebService portion of it with a thin Nancy controller to route the calls and return JSON. Since most of the processing time is spent chewing on the files Nancy's overhead isn't an issue and Nancy made it dead simple to code.
Nice to hear from someone using it for a real project and use case. I might consider it next time I get a chance!
Nancy is super duper