Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Another contender is <a href="http://www.asp.net/web-api" rel="nofollow">ASP.NET Web API</a> <a href="https://pfelix.wordpress.com/2012/03/05/asp-net-web-api-processing-architecture/" rel="nofollow">which uses WCF in self hosted scenario</a>.</p> <p>There are pros and cons but it all depends what you need now vs. latter, what is your level of expertise, technology commitment and what are the design trade-offs. </p> <p>It depends what you mean by reliable. One technology is not necessarily more or less reliable. There are many factors that go into reliability.</p> <p>These are some of the few pros/cons in no particular order, preference or completeness.</p> <p><strong>ASP.Net MVC / WebApi / ServiceStack</strong></p> <p>Pros:</p> <ul> <li>Setup and running within minutes for basic scenario (have URL get some JSON data)</li> <li>Simple to configure. </li> <li>REST setup straight forward.</li> <li>Complete control over routing.</li> <li>JSON native support (ASP.NET Web API can automatically serialize<br> your model to JSON, XML, or some other format, and then write<br> the serialized data into the body of the HTTP response<br> message.)</li> </ul> <p>Cons:</p> <ul> <li>Cannot describe your service to a consumer: no api like WSDL exist as of yet that can tell the client data types, operations and service requirements</li> <li>Transport security only - point-to-point security</li> <li>No message level security</li> <li>No Service Discovery protocols (as of now)</li> <li>No Message routing</li> <li>No multi-protocol support e.g. tcp</li> <li>Single hosting scenario (IIS - this can be a pro too)</li> </ul> <p><strong>WCF</strong></p> <p>Pros:</p> <ul> <li>Multi-protocol support</li> <li>Transport and Message security</li> <li>Highly configurable and inter-operable</li> <li><a href="http://blogs.msdn.com/b/carlosfigueira/archive/2011/03/14/wcf-extensibility.aspx" rel="nofollow">Very extensible</a></li> <li>Supports various messaging scenarios e.g. routing, duplex, pub/sub, queuing, etc.</li> <li>Lots of knobs for shaping messages and internal workings</li> <li>Wide variety of hosting scenarios (IIS/WAS, Windows Service, Console)</li> </ul> <p>Cons:</p> <ul> <li>Steep learning curve</li> <li><a href="http://msdn.microsoft.com/library/bb412172.aspx" rel="nofollow">REST story weak</a> (yes webHttpBinding exists but try explaining to someone TemplateURI and WebInvoke/Web get and BodyStyle) </li> <li>Lots of knobs</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. PO.Net options for JSON API?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPetar Vučetin
    1. USPetar Vučetin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO.Net options for JSON API?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI wish I could vote twice for this.. great answer
      singulars
      1. PO
      1. USMilkyWayJoe
    2. CONot only does ServiceStack have native JSON support, it has the fastest available for .NET: http://www.servicestack.net/benchmarks/ ServiceStack also supports JSON, XML as well as SOAP, JSV and CSV out-of-the-box. It also supports more hosts than HTTP with Redis and RCON hosts built-in. This question looks at WebApi vs ServiceStack in detail http://stackoverflow.com/q/9699083/85785
      singulars
      1. PO
      1. USmythz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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