title: Internal Web App: Do I need an API?
body: <p>I'm creating a new web application for internal use at work with internal data, and have been exploring tech stack options. I've used a REST API for another internal web app (also using internal SQL Server data), but then I read this today at <a href="http://www.meteorpedia.com/read/REST_API" rel="nofollow noreferrer" title="meteorpedia">Meteorpedia</a></p>
  <blockquote>
  <p>A common question is how to create a REST API with Meteor. First, it's critical to understand that if you are making an API for your own apps and tools, you've got it wrong! We hope it's very clear that between the server and client, you have a bidirectional DDP connection that handles realtime syncing of published data (see Publish and Subscribe in the docs).</p>
  </blockquote>
  <p><strong>So it seems I've got it wrong!</strong> I thought I needed an API to get data to my web app; that's what all the tutorials and articles seem to deal with. Where do I go to learn how else to do it? Or is this just something that Meteor offers and other front-end frameworks don't necessarily?</p>
  <p><strong>EDIT: Some more details:</strong> This app will be used by probably less than 10 people, the database is SQL Server. It won't be used on mobile, and the data doesn't need to be queried from elsewhere (it's sensitive data, so at the very least it would have to be an authenticated API).</p>