Hi,
1) hire a solution architect, make team members listen to him and make sure he's not a complete moron and architect by name only :) 2) having a solid naming convention should help, you could also look on how to actually make web APIs here: http://symfony.com/video/26/designing-http-interfaces-and-restful-web-services/English (it should give you a pretty good idea how things should look like). And the number of users doesn't count if the solution is scalable. Have a nice day :) On Tuesday, November 6, 2012 12:05:57 PM UTC+2, Bilgin Arf wrote: > > Hi There, > What is the best way forward to create a base system with API that will > allow coders to develop all the features onto the system using the API > The idea is here to have the base system ready online with API well guided > and allow coders to develop modules/plugins for the system using only the > API. > > What are the things we need to be careful and what is the best way forward > please ? > > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
