The Little Guy Posted March 10, 2012 Share Posted March 10, 2012 I was just thinking, if your service had an API, wouldn't it be best to build the API, and use the API within the site, instead of building two separate interfaces, one for the site and one for the API... What are your thoughts on that? Example, it would be like facebook using their own API to build facebook. The really only difference might be that they don't have to do HTTP requests to the API. Link to comment https://forums.phpfreaks.com/topic/258617-site-built-upon-your-own-api/ Share on other sites More sharing options...
trq Posted March 10, 2012 Share Posted March 10, 2012 I was just thinking, if your service had an API, wouldn't it be best to build the API, and use the API within the site, instead of building two separate interfaces, one for the site and one for the API... What are your thoughts on that? Yeah, that makes perfect sense and is indeed how you would do it, and if you use an MVC type of approach you should be able to execute controller/actions without making any http request. Link to comment https://forums.phpfreaks.com/topic/258617-site-built-upon-your-own-api/#findComment-1325694 Share on other sites More sharing options...
xylex Posted March 10, 2012 Share Posted March 10, 2012 AWS is the result of doing just that - their infrastructure is built across secure API's for their own e-commerce platform, and then they opened those API's up to the public for a whole new revenue stream. Link to comment https://forums.phpfreaks.com/topic/258617-site-built-upon-your-own-api/#findComment-1325716 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.