Separate REST JSON API server and client? [closed]

by

At Boundless, we’ve gone deep with option #2 and rolled it out to thousands of students. Our server is a JSON REST API (Scala + MongoDB), and all of our client code is served straight out of CloudFront (ie: www.boundless.com is just an alias for CloudFront).

Pros:

  • Cutting-edge/exciting
  • A lot of bang for your buck: API gives you basis for your own web client, mobile clients, 3rd party access, etc.
  • exceedingly fast site loading / page transitions

Cons:

  • Not SEO friendly/ready without a lot more work.
  • Requires top-notch web front-end folk who are ready to cope w/ the reality of a site experience that is 70% javascript and what that means.

I do think this is the future of all web-apps.

Some thoughts for the web front end folks (which is where all the new-ness/challenge is given this architecture):

  • CoffeeScript. Much easier to produce high-quality code.
  • Backbone. Great way to organize your logic, and active community.
  • HAMLC. Haml + CoffeeScript templates => JS.
  • SASS

We’ve built a harness for our front-end development called ‘Spar’ (Single Page App Rocketship) which is effectively the asset pipeline from Rails tuned for single page app development. We’ll be open-sourcing within the next couple of weeks on our github page, along with a blog post explaining how to use it and overall architecture in greater detail.

UPDATE:

With respect to people’s concerns with Backbone, I think they are over-rated. Backbone is far more an organizational principle than it is a deep framework. Twitter’s site itself is a giant beast of Javascript covering every corner-case across millions of users & legacy browsers, while loading tweets real-time, garbage collect, display lots of multimedia, etc. Of all the ‘pure’ js sites I’ve seen, Twitter is the odd one out. There have been many impressively complicated apps delivered via JS that fare very well.

And your choice of architecture depends entirely on your goals. If you are looking for the fastest way to support multiple clients and have access to good front-end talent, investing in a standalone API is a great way to go.

More Related Contents:

  1. Undefined method ‘task’ using Rake 0.9.0
  2. Understanding :source option of has_one/has_many through of Rails
  3. Implement “Add to favorites” in Rails 3 & 4
  4. How to empty a Heroku database
  5. Turn off CSRF token in rails 3
  6. Stubbing authentication in request spec
  7. Rails’ link_to method: GETing when it should DELETE
  8. Rails 3.1: Engine vs. Mountable App
  9. rails – “WARNING: Can’t verify CSRF token authenticity” for json devise requests
  10. Adding a column to an existing table in a Rails migration
  11. “Who’s Online” using Devise in Rails
  12. default_url_options and rails 3
  13. rmagick gem install “Can’t find Magick-config”
  14. Thin web server: `start_tcp_server’: no acceptor (RuntimeError) after git branch checkout
  15. Rails 3 library not loading until require
  16. Clarification on how to use “thumbs_up” voting gem with Rails 3
  17. using Liquid variables inside of a liquid tag call
  18. Rails 3.1 asset pipeline and manually ordered Javascript requires
  19. Rails 3 paperclip vs carrierwave vs dragonfly vs attachment_fu [closed]
  20. Delete multiple records using REST
  21. How do I fetch a single model in Backbone?
  22. How can I specify a gem to pull from a private github repository?
  23. Rails 3 render action from another controller
  24. rails 3 activerecord order – what is the proper sql injection work around?
  25. How do I secure REST API calls?
  26. Rails 3 – how do I avoid database altogether?
  27. Setting up a polymorphic has_many :through relationship
  28. ActiveRecord Find All not sorting by ID?
  29. Does accepts_nested_attributes_for work with belongs_to?
  30. Default_url in Paperclip Broke with Asset Pipeline Upgrade

Leave a Comment