Websocket API to replace REST API? [closed]

by

Not to say that the other answers here don’t have merit, they make some good points. But I’m going to go against the general consensus and agree with you that moving to websockets for more than just realtime features is very appealing.

I am seriously considering moving my app from a RESTful architecture to more of an RPC style via websockets. This is not a “toy app”, and I’m not talking about only realtime features, so I do have reservations. But I see many benefits in going this route and feel it could turn out to be an exceptional solution.

My plan is to use DNode, SocketIO, and Backbone. With these tools, my Backbone models and collections can be passed around from/to client and server by simply calling a functions RPC-style. No more managing REST endpoints, serializing/deserializing objects, and so forth. I haven’t worked with socketstream yet, but it looks worth checking out.

I still have a long way to go before I can definitively say this is a good solution, and I’m sure it isn’t the best solution for every application, but I’m convinced that this combination would be exceptionally powerful. I admit that there are some drawbacks, such as losing the ability to cache resources. But I have a feeling the advantages will outweigh them.

I’d be interested in following your progress exploring this type of solution. If you have any github experiments, please point me at them. I don’t have any yet, but hope to soon.

Below is a list of to-read-later links that I’ve been collecting. I can’t vouch that they are all worthwhile, as I’ve only skimmed many of them. But hopefully some will help.

Great tutorial on using Socket.IO with Express. It exposes express sessions to socket.io and discusses how to have different rooms for each authenticated user.

Tutorial on node.js/socket.io/backbone.js/express/connect/jade/redis with authentication, Joyent hosting, etc:

Tutorial on using Pusher with Backbone.js (using Rails):

Build application with backbone.js on the client and node.js with express, socket.io, dnode on the server.

Using Backbone with DNode:

More Related Contents:

  1. access MONGODB on remote server [closed]
  2. “SyntaxError: Unexpected token < in JSON at position 0"
  3. Send message to specific client with socket.io and node.js
  4. Sending message to a specific connected users using webSocket?
  5. Good beginners tutorial to socket.io? [closed]
  6. Returning data from Axios API
  7. Sharing websocket across browser tabs?
  8. How to use the ‘main’ parameter in package.json?
  9. Socket.io – Manual reconnect after client-side disconnect
  10. How do I pass command line arguments to a Node.js program?
  11. module.exports vs exports in Node.js
  12. Mocha / Chai expect.to.throw not catching thrown errors
  13. Callback after all asynchronous forEach callbacks are completed
  14. Why does a while loop block the event loop?
  15. Best way to call an asynchronous function within map?
  16. How can i export socket.io into other modules in nodejs?
  17. Rest with Express.js nested router
  18. What is NODE_ENV and how to use it in Express?
  19. Module not found: Error: Can’t resolve ‘crypto’
  20. Creating Rooms in Socket.io
  21. How do I upload a base64 encoded image (string) directly to a Google Cloud Storage bucket using Node.js?
  22. How many concurrent setTimeouts before performance issues?
  23. Eslint does not allow static class properties
  24. Environment detection: node.js or browser
  25. In the `import` syntax of ES6, how is a module evaluated exactly?
  26. Curly brackets (braces) in Node.js ‘require’ statement
  27. Checking if a message was sent from a DM not working
  28. Spawn and kill a process in node.js
  29. node.js mongodb select document by _id node-mongodb-native
  30. what happens when a Promise never resolves? [duplicate]

Leave a Comment