I already have an asp.net mvc-based site that mainly talks about my service. The service level is designed so that external applications can access it as an API (probably similar to Twitter).
Think of it as an accurate twitter. Functions Used:
- Authentication (password, facebook, twitter, OpenID).
- CRUD for data.
Now my problem is choosing the RESTful API framework. I thought of the following:
- If I use asp.net mvc, will I limit myself anyway? For example, the page life cycle, etc.
- I try to stay away from WCF since I heard that it is too big and bulky.
- How well will ADO.NET data services work with the design of my application?
- How about OpenRasta ?
I think that I have developed both my service level and the mvc application (sessions, etc.) to scale horizontally so far. Not sure what it takes to scale the API.
source
share