CODEWITHSUNDEEP
javascriptapifrontendbackend
Matthew Brown
Matthew Brown

Reputation: 1052

backbonejs frontend bound via an api to a nodejs backend

Here's my concept:

  'Javascript Frontend in the Browser (eg. Backbonejs)'
            Handles most of the logic

                       |
                 'RESTful API'
                       |
                       V

     'API Backend (eg. nodejs, python, ruby)'
             Only handles raw data

And my question is: Is this a stable architecture? Doesn't it create more possible points of failure than a generic python/ruby/java web app? Also, is it a good idea to base the frontend on an API that could, one day, become publicly accessible?

Upvotes: 0

Views: 391

Answers (1)

sir-pinecone
sir-pinecone

Reputation: 251

I've built multiple tools at work using this exact design. I haven't had any major issues at all. The most complex part was the use of web sockets to define an API that Backbone interacts with, but you can easily swap that with ajax for reduced complexity.

Upvotes: 1

Related Questions