I have read about various issues in using HAProxy and socket-io (websockets mode). I am currently working on a project that's heading towards that direction - anyone has anything to share on that front?
The Trello Tech Stack
11–20 of 96 posts
Re: The Trello Tech Stack
#12Nice job, guys. I love this architecture. This looks a lot like my dream stack for future web work.
Would love to hear some more about the "bleeding" experiences you've had.
Re: The Trello Tech Stack
#13Great write up. Hopefully that ephemeral data in Redis can scale.
They could have used something like Pusher for about half of their implementation (the websockets, message pushing, polling, etc)
I bring this up because I built an OSS Pusher clone[1], for those people that want to deploy their own, built on the Play! framework.
Re: The Trello Tech Stack
#14I have read about various issues in using HAProxy and socket-io (websockets mode). I am currently working on a project that's heading towards that direction - anyone has anything to share on that front?
nginx supports http1.1 reverse proxying as of a few weeks ago http://wiki.nginx.org/HttpProxyModule
Mikito Takada (Zendesk) has some really helpful information regarding socket.io + haproxy specific workarounds via http://blog.mixu.net/2011/08/13/nginx-websockets-ssl-and-soc...
Re: The Trello Tech Stack
#15Great write up. Hopefully that ephemeral data in Redis can scale. They could have used something like Pusher for about half of their implementation (the websockets, message pushing, polling, etc) I bring this up because I built an OSS Pusher clone[1], for those people that want to deploy their own, built on the Play! framework. [1] https://github.com/danbeaulieu/PushPlay
There's also this ruby implementation that plays nice with all the pusher libs https://github.com/stevegraham/slanger
Re: The Trello Tech Stack
#16This post raises a few questions for me... and perhaps some one more versed in these stacks can provide answers. - Does the use of CoffeeScript alleviate the MC Escher-esque quality of callbacks within closures involved in working with Javascript on both the server and client (and the data store)? I can totally see the appeal of CoffeeScript's syntax. Giving the programmers something different to look (and learn) at…
- Daniel is going to write another post detailing this. The answer is that when you combine CoffeeScript and a good async library, you can indeed get rid of that stuff.
- MoNsteR? =)
Re: The Trello Tech Stack
#17It seems Socket.io has not had any contenders yet..
Re: The Trello Tech Stack
#18Awesome job guys. I'm really digging this stack. It is giving me motivation to learn more about Backbone.js
Re: The Trello Tech Stack
#19This post raises a few questions for me... and perhaps some one more versed in these stacks can provide answers. - Does the use of CoffeeScript alleviate the MC Escher-esque quality of callbacks within closures involved in working with Javascript on both the server and client (and the data store)? I can totally see the appeal of CoffeeScript's syntax. Giving the programmers something different to look (and learn) at…
LNMR... um... LaMiNaR? RoMuLaN?
Re: The Trello Tech Stack
#20If you could do this over again, would you still choose socket.io for websockets, or would you go with something else like PusherApp?