Some instructions on how to run ServiceStack as a self-hosted daemon (or behind an Nginx reverse proxy):
All of ServiceStack live demos runs on an Ubuntu vServer under Nginx/MonoFastCGI including the Razor Rockstars live demos:
http://razor.servicestack.net - ASP.NET Hosted live demo powered by Linux / Nginx / MonoFastCGI
http://razor-console.servicestack.net - Self-Hosted Console App hosted behind Nginx Reverse Proxy
They also discuss their experiences with ServiceStack, and how they've customized it to their liking:
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.
Glad to see it's still moving forward.
I think the framework is good as it is, but knowing about big names backing it would give me more faith going forward.
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:
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
Whilst I go into a bit more about our technical setup at:
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.
So far, I've been able to achieve everything I need using just WebAPI and Attribute Routing. 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'.
Edit - Reworded.
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
F# Web Services on any platform in and out of a web server!
Async, Cached Twitter API Proxy in F#
C# + F# Self Hosting Examples