by

ServiceStack is on InfoQ! TL;DR and Links

Adding to ServiceStack’s great run in 2012 I was approached by InfoQ to find some details about ServiceStack vs WCF, why we created it, it’s advantages over WCF and the philosophical differences in development styles and approach between ServiceStack and high-level Microsoft libraries and application frameworks. The resulting interview contains my thoughts on the best development and remote services practices, WCF’s architecture, its use of SOAP/WS-*, why heavy abstractions and artificial server-side programming models are not ideal, how pragmatic and simpler serialization formats are better suited for services, why message-based designs are preferred by most other frameworks, the state of .NET Open Source and much more.

The entire interview is quite long which ran to 8,000 words that as a result was split up and published in two articles. To make it easier to find and navigate the content, I’ve published a TL;DR summary, including related questions, table of contents and all embedded links used below:

Interview With Demis Bellot, Project Lead of ServiceStack – Part 1:

InfoQ: What problems do you see in Microsoft’s approach to Services and how does ServiceStack try to tackle it?

Interview With Demis Bellot, Project Lead of ServiceStack – Part 2

InfoQ: What exactly is a message-based Web service?
InfoQ: You recently introduced a razor engine making ServiceStack a more complete web framework than just a web services framework – what was the motivation behind that?
InfoQ: Are there any scenarios where you think WCF/Web API/MVC might be better suited than ServiceStack?
  • MVC better at large write-heavy server-generated websites
  • ServiceStack is optimizing for SPA’s like Backbone.js, AngularJS, Dart Web Components, etc
  • WebApi better choice for building server-side driven systems with HATEOS Restrictions
  • ServiceStack better choice for maximum re-use and utility of your services
  • MVP and Microsoft Gold Partners will want to continue to choose the prescribed Microsoft stacks
  • ServiceStack will optimize for alternative platforms (e.g. Mono), Clouds (EC2, Google CE), RDBMS (Sqlite, MySql, Pgsql, etc), Redis/NoSQL
InfoQ: Microsoft has collaborated with open source projects in the past (JQuery, NuGet for e.g.) and MS folks like Scott Hanselman seem quite open about adopting good open source solutions into the MS default stack wherever possible – do you foresee any such collaborations that could benefit the .NET community in general?
InfoQ: You made a comment recently on one of the forums – “I’m hoping next year to be even better, as I have a few things planned that should pull us away from the other frameworks” – would you elaborate what features you have in mind for the future?
ServiceStack set to make exciting new product announcements in 2013. Current road map includes:
  • Merging the Async branch and its async pipeline
  • Create new fast Async TCP Endpoints
    • Enable fast, native adapters for node.js and Dart server processes
  • Enable integration with more MQ Endpoints (i.e. RabbitMQ and ZeroMQ)
  • VS.NET Integration and our improved solution for WCF’s ‘Add Service Reference’
  • Integrated Development workflow and story for Mono/Linux
    • Enable automated deployment story to Amazon EC2 and Google Compute Engine clouds
  • Signed and Long-term stable commercial packages
  • Starter templates around popular Single Page App Stacks: Backbone.js, AngularJS, Yeoman and Dart
  • Starter templates for creating CRM and SharePoint-enabled support systems
  • Website re-design and improved documentation

If you have the time I recommend reading the entire interview, otherwise hopefully these bulleted points can help you find the bits you’re interested in sooner.