Django Developers Survery Results

Post by ceyhunkazel » Thu, Jul 09, 2015, 7:29 PM UTC

aaronbasssett wrote: post #22

knes wrote: post #20

I see a lot of feedback about how difficult it is to use websockets or add real-time features to an Django app. I work at Pusher ( http://pusher.com ) and this is exactly what we do. We make it dead simple for any developers to use websockets and handle the scaling and maintenance for them. We even have custom libraries for Django such as Django-pusherable https://github.com/pusher/django-pusherable Associated blog p…

Thanks for a mention of the library/blog post :) I also did a talk at this year's DjangoCon Europe about building realtime apps in Django which covers integrating Swampdragon[1] and Pusher in Django. Video of the talk isn't up yet but the slides are on Speakerdeck[2] and my example code is on Github[3]. [1]: http://swampdragon.net/ [2]: https://speakerdeck.com/aaronbassett/effortless-real-time-ap... [3]: https://gith…

Could you compare swampdragon vs Pusher? Ease of use, cost, overall experience etc.. Any guide which to choose?

Post by aaronbasssett » Sun, Jul 19, 2015, 11:03 PM UTC

ceyhunkazel wrote: post #31

aaronbasssett wrote: post #22

Earlier quoted context omitted.

Thanks for a mention of the library/blog post :) I also did a talk at this year's DjangoCon Europe about building realtime apps in Django which covers integrating Swampdragon[1] and Pusher in Django. Video of the talk isn't up yet but the slides are on Speakerdeck[2] and my example code is on Github[3]. [1]: http://swampdragon.net/ [2]: https://speakerdeck.com/aaronbassett/effortless-real-time-ap... [3]: https://gith…

Could you compare swampdragon vs Pusher? Ease of use, cost, overall experience etc.. Any guide which to choose?

It is not a mutually exclusive decision. I used Swampdragon's serialisers with Pusher (and hopefully in future releases Swampdragon will share its serialisers with DRF as well).

In terms of ease of use, Pusher is easiest to setup as it is a PaaS service so you don't need to install anything. Swampdragon has a slight advantage that you can run it locally without any outside dependencies, which is nice for development.

Scaling and cost, well it depends on your current architecture. Swampdragon you'll need to scale out/maintain your own Redis and Tornado servers whereas with Pusher it's a fixed cost and you don't have to worry about scaling/bursting etc.

A pattern I've seen personally is people start with self-hosting until they reach more concurrent connections than a single server can comfortably handle and then switching to a PaaS service like Pusher.

Re: Django Developers Survery Results

Re: Django Developers Survery Results