That's how I prefer to structure my apps these days. It lends itself more naturally to the "disposable front-end" idea (a la Guy Kawasaki's writings). I prefer

That's how I prefer to structure my apps these days. It lends itself more naturally to the "disposable front-end" idea (a la Guy Kawasaki's writings). I prefer to push as much business-logic into the API as I can, and have the client be thin and quick. I also prefer to have the API be rock-solid (well tested, documented, etc) while the front-ends are more experimental and less stable. In the very early stages of a startup (MVP phase) this might arguably be overkill. But as the team grows, you'll be happy that the backend and frontend folks are in different repos (as they probably have very different development methodologies). And as your userbase/traffic scales up, you'll be able to allocate server resources very efficiently. An added benefit is that (depending on the front-end you use) porting to PhoneGap/Cordova and making a mobile app out of it is a breeze. One word of caution as you jump into single-page front-ends: It's worth your time and effort to figure out an elegant SEO solution early on. I prefer prerender.io, but there are many good options.