title: Best practices for JSON responses on a MS-SQL and NODE architecture
body: <p>GoodDay, starting experimentation on Node against MsSql on Azure for solutions very data-centric.</p>
  
  <p><strong>What would be best practice for this short of architecture ?</strong> <br>
  (all communication to the DB to be made trough Store Procedures, obviously)</p>
  
  <p>So far, we are experimenting with <a href="https://www.npmjs.com/package/mssql" rel="nofollow noreferrer">https://www.npmjs.com/package/mssql</a> and found that output parameters last a while sometimes until they become ready...</p>
  
  <p>so we have thought into:</p>
  
  <ul>
  <li>SP call parameters as separate input-Parameters (easier to treat in SQL)</li>
  <li>Data to node application as a single (sometimes composed) JSON, as a recordset</li>
  <li>SP execution code trough RETURN (202 ok, rest of codes as w3c web codes)</li>
  <li>Return message, in case of error, trough an output parameter.</li>
  </ul>
  
  <p><strong>Any indications ?</strong></p>
  
  <p>I found very interesting this binomia (Node + MsSQL), strength from one side, flexibility and speed from the other one ...</p>