StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I'm glad to hear you are considering <a href="http://www.servicestack.net" rel="noreferrer">ServiceStack</a> :), It's a framework that's been under development over the last few years, born out of the frustrations and friction caused by the rigidness of .NET's existing .asmx and WCF SOAP web services framework. I found none of the existing frameworks promoted a code-first conventional approach that follows Martin Fowlers best-practices <strong><a href="http://martinfowler.com/eaaCatalog/dataTransferObject.html" rel="noreferrer">Data Transfer Object Pattern</a></strong> which I believe is instrumental in being able to develop well-defined, less-chatty, cacheable and re-usable web services.</p> <p>It's primary goals are:</p> <ul> <li>Promoting best-practices C# development - loosely coupled, testable (endpoint/format agnostic) services. </li> <li>Best-practices Web service development - Your web service contract is the most important interface you're likely ever to make, as such it should be code-first, strong-typed and well-defined.</li> <li>Re-usable, Model driven architecture - Note your services inherit from a dep-free IService[of T] which can also be re-used in Message Queue services.</li> <li>Cross-platform - Supports both Windows (.NET) / Linux/OSX (MONO)</li> <li>Performance - Run-time reflection-free and uses only the fastest .NET components for all of its features</li> <li>Cacheability - Caching is an important part of high-performance, scalable services as such it is sometimes important to have fine-grained control over your caching, be able to cache the most optimal result (i.e gzipped response) and have a <a href="https://github.com/ServiceStack/ServiceStack/wiki/Caching" rel="noreferrer">variety of caching providers</a>. See <a href="http://servicestack.net/ServiceStack.Northwind/" rel="noreferrer">Northwind example</a>.</li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload