Why Service stack

I've read good things about Service Stack across the web. I've recently started a new job where its their Api stack of choice.

Having been a Web Api follower for years its hard to wrap my brain around SS. A couple of stand out issues is the flippant use of java terms (like DTO) thrown around their documentation like its a good thing. Another issue I have that drives me up the wall about this is that their routes are tied to the DTO request/response instead of the methods that respond to the service. You hear a lot about code smell, to me thats a prime example. Why would the response/request object need to know about a route. Even typing that sentence makes me cringe…

Here's an example link:

http://ift.tt/1MDuCPC

by SalizarMarxx via /r/csharp

Leave a Reply