TableController vs ApiController in Azure Mobile Apps

Question

I'm just getting started with Mobile Apps. I'm used to making APIs with ApiController of Web API.

The default project template for Mobile Apps in VS2015 comes with a sample TodoItemController that inherits from TableController. It looks like there are some CRUD operations installed out-of-the-box in TableController and each data object must be of type ITableData.

Ideally, I'd like to skip TableController and implement things my own way with ApiController.

My question is, what are the ramifications of ditching TableController if any? Is there any tight-coupling between App Service and the use of TableController?

Answer 1

The TableController is coupled with the client SDK's table logic, and provides all the right logic & columns for the interactions needed for querying, offline sync, etc.

You can use API Controllers just fine, it mainly will depend on what features you want to use.