SheppardDigital
asked on
Web Service, Admin Interface, different applications or same application?
I know this question doesn't technically have a 'right' answer, but I'm hoping to get some input on what would be considered best practice.
Lately I'm building a lot of Web Services that are to be used by mobile applications, most of which also require a web interface to be able to manage the data.
I've been building the admin interface and api as part of one PHP application, whereby both the API and the admin interface have direct access to the SQL database.
I'm wondering if separating them and having the admin interface talk to the API, and only the API talk to the database is a more appropriate way of doing things?
Any suggestions or advice would be appreciated.
Lately I'm building a lot of Web Services that are to be used by mobile applications, most of which also require a web interface to be able to manage the data.
I've been building the admin interface and api as part of one PHP application, whereby both the API and the admin interface have direct access to the SQL database.
I'm wondering if separating them and having the admin interface talk to the API, and only the API talk to the database is a more appropriate way of doing things?
Any suggestions or advice would be appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER