I think the framework is good as it is, but knowing about big names backing it would give me more faith going 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: 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
The Redis MQ Support is heavily utilized, where all offline tasks and sync services go through, you can read more about it at:
https://github.com/ServiceStack/ServiceStack/wiki/Messaging-...Whilst I go into a bit more about our technical setup at: http://stackoverflow.com/questions/12537521/host-application...
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.