Can anyone recommend a good setup for Mono? In my tests, mono-fascgi + nginx has been extremely slow at handling requests. Wanted to give this a spin some time ago, as well as ASP.NET MVC, but I couldn't get decent performance on linux.
I'd like to add that I've used various parts of the ServiceStack suite of products before and I've always found them to be very easy to use, and reliable. Also, the maintainer was always good about responding to bug requests and following up about them.
Yes I've been working for StackOverflow for over a year...
We use ServiceStack to handle all of StackOverflow Careers BackOffice web services.
StackOverflow uses ServiceStack's JSON Serializer (.NET's fastest) for all its JSON serialization needs:
http://blog.stackoverflow.com/2012/02/stack-exchange-open-so...
Whilst StackOverflow Careers makes uses the entire ServiceStack's technology suite:
- ServiceStack Web Service Framework to handle all BackOffice services
- ServiceStack's JSON serializer
- ServiceStack's C# Redis Client
- ServiceStack OrmLite (along with Linq2Sql + Dapper)
- Bundler: Our node.exe based - for all compilation and minifiying of less, css, js assets.
- Built-in MQ support in ServiceStack which lets us re-use existing Web Services in a MQ Host
StackExchange is very supportive considering any enhancements I need to do to make ServiceStack work better for our usage at work is done on Company time, i.e. The newer Redis MQ Server implementation to support parallel processing of MQ messages was mostly done at work. As well as any bug fixes, regressions we run into.
I don't think it's a StackOverflow project per se but it is used to power their Careers website. While it may not a big name backing it, I think it's a fairly popular .NET OSS project with a strong team/community behind it.
I've been using ServiceStack + AngularJS in a project for a couple of months now, and it's been the bees knees. I'm excited to try out the new API style.
As someone who has been knee deep in WCF for years and now diving into WebAPI I still don't understand the real differences between ServiceStack and WebAPI. It seems like this answer was written well before WebAPI was released or fully baked. Now that it's out is there anything new you can tell us?
So far, I've been able to achieve everything I need using just WebAPI and Attribute Routing[1]. Is there something fundamentally different you can demonstrate or describe for us? I did some research on ServiceStack and the only thing that stuck was that you also had your own serialization libraries too. (Although I still prefer JSON.Net) I guess what I'm looking for are the Can Dos and the Can't Dos too. Not just 'we like this approach instead'.
Which explains the natural benefits of the design ServiceStack promotes (no other MS fx promotes this).
We strongly believe that message-based services promote the best practices for remote service development, something we've benefitted from for years.
ServiceStack is different in that it can support the same service running on SOAP, MQ endpoints (in addition to JSON, XML, JSV, CSV out-of-the-box) it even can be re-used as the controller for HTML web pages, see: http://razor.servicestack.net
