Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Different Users, communities have different API requirements, in the way they want to expose their resources. So there can never be a 'one fit all' solution from askbot. Also a site that runs askbot will have lots of Data overtime, which can be monetized by exposing a solid RESTful API. Only the site owners will best know what to and what NOT to expose, to other developers and partners.

So in my view the API for Askbot, should be very loosely coupled, like a managed API server. Its good if the design pattern encourages all these. It should also act like a load balancer to a larger extent, intelligently cache same requests (act like memcached for API requests). So all this will not slow down and affect the Site APP server.

We need all such good design patterns for the API and this is a huge topic to debate. We might also need things like Webhooks.

Please see all the managed API companies - APIgee, emergentone.com and Heroku's managed api's. They do API management for any APP, they give and manage an API server for your APP. Check the services they offer, you will appreciate my points of view.

Different Users, communities have different API requirements, in the way they want to expose their resources. So there can never be a 'one fit all' solution from askbot. Also a site that runs askbot will have lots of Data overtime, which can be monetized by exposing a solid RESTful API. Only the site owners will best know what to and what NOT to expose, to other developers and partners.

So in my view the API for Askbot, should be very loosely coupled, like a managed API server. Its good if the design pattern encourages all these. It should also act like a load balancer to a larger extent, intelligently cache same requests (act like memcached for API requests). So all this This will not slow down and affect the Site APP server.

We need all such good design patterns for the API and this is a huge topic to debate. We might also need things like Webhooks.

Please see all the managed API companies - APIgee, emergentone.com and Heroku's managed api's. They do API management for any APP, they give and manage an API server for your APP. Check the services they offer, you will appreciate my points of view.

click to hide/show revision 3
improved answer, perfection. huh. :)

Different Users, communities have different API requirements, in the way they want to expose their resources. So there can never be a 'one fit all' solution from askbot. askbot side. Also a an askbot site that runs askbot will have lots of Rich Data overtime, which can be monetized by exposing a solid RESTful API. Only the And only the Askbot site owners will best know - what to and what NOT to expose, to other developers and partners.

So in my view view, the API for Askbot, should be very loosely coupled, like a managed API server. Its good managed API server. It is good, if the design pattern encourages all these. It should such things. If you think as a network engineer, a managed API also act like serves as a load balancer to a larger extent, intelligently cache same requests (act (doing things like memcached for API requests). This will not slow down and affect the Site APP server.server anytime.

We need all such good design patterns for the API and this is a huge topic to debate. We might also need things like Webhooks.

Please see all the managed API companies - APIgee, emergentone.com and Heroku's managed api's. to setup an externally managed API. They do API management for any APP, DB. In short - they give and manage an API server for your APP. Check APP. So its super easy to expose, control (authorize, manage resource access control) and also scale your API server on more requests. Do check in detail the services they all offer, you will appreciate my points of view.