I'd have no problem having a single API service. Just separate your API classes and routes well so it's easy to understand and maintain. You may end up having multiple servers, but running the same apps and services, only to ensure higher availability. As well, to future proof things, you may build it to ensure you can have multiple versions of your API down the line, so all apps don't need to be updated at once should a major refactoring of some sort take place. For instance, a service may be running at https://site.com/API/v1/service/method. If you ever made breaking changes to the API, you could build that at a v2 path and continue to support the v1 route as well.
Our company runs many apps, mobile and web, and they are all served by a single set of [versioned] APIs on a load balanced cluster at EC2. Best of luck -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/b383b1ef-1da7-4cc4-8e2d-056eaad2a2e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
