Alternatives to Django Channels logo

Alternatives to Django Channels

Twisted, Tornado, Celery, Pushpin, and asyncio are the most popular alternatives and competitors to Django Channels.
88
116
+ 1
1

What is Django Channels and what are its top alternatives?

It does this by taking the core of Django and adding a fully asynchronous layer underneath, running Django itself in a synchronous mode but handling connections and sockets asynchronously, and giving you the choice to write in either style.
Django Channels is a tool in the Frameworks (Full Stack) category of a tech stack.
Django Channels is an open source tool with 5.3K GitHub stars and 728 GitHub forks. Here’s a link to Django Channels's open source repository on GitHub

Top Alternatives to Django Channels

  • Twisted
    Twisted

    Twisted is an event-driven networking engine written in Python and licensed under the open source ​MIT license. Twisted runs on Python 2 and an ever growing subset also works with Python 3. Twisted also supports many common network protocols, including SMTP, POP3, IMAP, SSHv2, and DNS. ...

  • Tornado
    Tornado

    By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. ...

  • Celery
    Celery

    Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well. ...

  • Pushpin
    Pushpin

    Pushpin is a reverse proxy server that makes it easy to build realtime web services. The project is unique among realtime push solutions in that it is designed to address the needs of API creators. ...

  • asyncio
    asyncio

    This module provides infrastructure for writing single-threaded concurrent code using coroutines, multiplexing I/O access over sockets and other resources, running network clients and servers, and other related primitives. ...

  • REST
    REST

    An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies. ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

Django Channels alternatives & related posts

Twisted logo

Twisted

52
84
10
Event-driven networking engine written in Python
52
84
+ 1
10
PROS OF TWISTED
  • 5
    Easy-to-understand concurrency
  • 3
    Twisted prevails
  • 1
    It works
  • 1
    Solid, flexible, powerful
CONS OF TWISTED
    Be the first to leave a con

    related Twisted posts

    Tornado logo

    Tornado

    336
    383
    165
    A Python web framework and asynchronous networking library, originally developed at FriendFeed
    336
    383
    + 1
    165
    PROS OF TORNADO
    • 37
      Open source
    • 31
      So fast
    • 27
      Great for microservices architecture
    • 20
      Websockets
    • 17
      Simple
    • 13
      Asynchronous
    • 10
      Python
    • 7
      Lightweight
    • 3
      Handles well persistent connexions
    CONS OF TORNADO
    • 2
      Event loop is complicated

    related Tornado posts

    Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

    See more
    Celery logo

    Celery

    1.4K
    1.4K
    269
    Distributed task queue
    1.4K
    1.4K
    + 1
    269
    PROS OF CELERY
    • 97
      Task queue
    • 62
      Python integration
    • 37
      Django integration
    • 29
      Scheduled Task
    • 18
      Publish/subsribe
    • 6
      Various backend broker
    • 6
      Easy to use
    • 5
      Great community
    • 4
      Free
    • 4
      Workflow
    • 1
      Dynamic
    CONS OF CELERY
    • 4
      Sometimes loses tasks
    • 1
      Depends on broker

    related Celery posts

    James Cunningham
    Operations Engineer at Sentry · | 18 upvotes · 1.4M views
    Shared insights
    on
    CeleryCeleryRabbitMQRabbitMQ
    at

    As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

    Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

    #MessageQueue

    See more
    Pulkit Sapra

    Hi! I am creating a scraping system in Django, which involves long running tasks between 1 minute & 1 Day. As I am new to Message Brokers and Task Queues, I need advice on which architecture to use for my system. ( Amazon SQS, RabbitMQ, or Celery). The system should be autoscalable using Kubernetes(K8) based on the number of pending tasks in the queue.

    See more
    Pushpin logo

    Pushpin

    10
    45
    3
    Reverse proxy for realtime web services
    10
    45
    + 1
    3
    PROS OF PUSHPIN
    • 3
      Open source
    CONS OF PUSHPIN
    • 1
      Worst community support

    related Pushpin posts

    asyncio logo

    asyncio

    89
    132
    13
    Asynchronous I/O, event loop, coroutines and tasks
    89
    132
    + 1
    13
    PROS OF ASYNCIO
    • 4
      Cooperative Multitasking
    • 4
      I/O Wait
    • 3
      Network Call
    • 2
      I/O bound computation
    CONS OF ASYNCIO
      Be the first to leave a con

      related asyncio posts

      Jelena Dedovic

      Investigating Tortoise ORM and GINO ORM...

      I need to introduce some async ORM with the current stack: Tornado with asyncio loop, AIOHTTP, with PostgreSQL and MSSQL. This project revolves heavily around realtime and due to the realtime requirements, blocking during database access is not acceptable.

      Considering that these ORMs are both young projects, I wondered if anybody had some experience with similar stack and these async ORMs?

      See more
      REST logo

      REST

      20
      173
      0
      A software architectural style
      20
      173
      + 1
      0
      PROS OF REST
      • 3
        Popularity
      CONS OF REST
        Be the first to leave a con

        related REST posts

        Node.js logo

        Node.js

        145.5K
        122.5K
        8.5K
        A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
        145.5K
        122.5K
        + 1
        8.5K
        PROS OF NODE.JS
        • 1.4K
          Npm
        • 1.3K
          Javascript
        • 1.1K
          Great libraries
        • 1K
          High-performance
        • 801
          Open source
        • 485
          Great for apis
        • 475
          Asynchronous
        • 420
          Great community
        • 390
          Great for realtime apps
        • 295
          Great for command line utilities
        • 81
          Websockets
        • 81
          Node Modules
        • 68
          Uber Simple
        • 59
          Great modularity
        • 57
          Allows us to reuse code in the frontend
        • 42
          Easy to start
        • 35
          Great for Data Streaming
        • 32
          Realtime
        • 28
          Awesome
        • 25
          Non blocking IO
        • 18
          Can be used as a proxy
        • 17
          High performance, open source, scalable
        • 16
          Non-blocking and modular
        • 15
          Easy and Fun
        • 14
          Easy and powerful
        • 13
          Future of BackEnd
        • 13
          Same lang as AngularJS
        • 12
          Fullstack
        • 11
          Fast
        • 10
          Cross platform
        • 10
          Scalability
        • 9
          Simple
        • 8
          Mean Stack
        • 7
          Great for webapps
        • 7
          Easy concurrency
        • 6
          React
        • 6
          Typescript
        • 6
          Fast, simple code and async
        • 6
          Friendly
        • 5
          Control everything
        • 5
          Its amazingly fast and scalable
        • 5
          Easy to use and fast and goes well with JSONdb's
        • 5
          Scalable
        • 5
          Great speed
        • 5
          Fast development
        • 4
          Isomorphic coolness
        • 4
          It's fast
        • 4
          Easy to use
        • 3
          Easy to learn
        • 3
          Easy
        • 3
          Great community
        • 3
          Not Python
        • 3
          Sooper easy for the Backend connectivity
        • 3
          TypeScript Support
        • 3
          Scales, fast, simple, great community, npm, express
        • 3
          One language, end-to-end
        • 3
          Less boilerplate code
        • 3
          Performant and fast prototyping
        • 3
          Blazing fast
        • 2
          Npm i ape-updating
        • 2
          Event Driven
        • 2
          Lovely
        CONS OF NODE.JS
        • 46
          Bound to a single CPU
        • 42
          New framework every day
        • 37
          Lots of terrible examples on the internet
        • 30
          Asynchronous programming is the worst
        • 23
          Callback
        • 18
          Javascript
        • 11
          Dependency hell
        • 11
          Dependency based on GitHub
        • 10
          Low computational power
        • 7
          Very very Slow
        • 7
          Can block whole server easily
        • 6
          Callback functions may not fire on expected sequence
        • 3
          Unneeded over complication
        • 3
          Unstable
        • 3
          Breaking updates
        • 1
          Bad transitive dependency management
        • 1
          Can't read server session
        • 1
          No standard approach

        related Node.js posts

        Nick Rockwell
        SVP, Engineering at Fastly · | 44 upvotes · 2M views

        When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

        So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

        React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

        Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

        See more
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5M views

        How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

        Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

        Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

        https://eng.uber.com/distributed-tracing/

        (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

        Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

        See more
        Django logo

        Django

        30.3K
        27.2K
        3.9K
        The Web framework for perfectionists with deadlines
        30.3K
        27.2K
        + 1
        3.9K
        PROS OF DJANGO
        • 643
          Rapid development
        • 476
          Open source
        • 409
          Great community
        • 359
          Easy to learn
        • 268
          Mvc
        • 219
          Beautiful code
        • 212
          Elegant
        • 196
          Free
        • 195
          Great packages
        • 182
          Great libraries
        • 71
          Restful
        • 69
          Powerful
        • 68
          Comes with auth and crud admin panel
        • 65
          Great documentation
        • 62
          Great for web
        • 48
          Python
        • 38
          Great orm
        • 36
          Great for api
        • 27
          All included
        • 22
          Fast
        • 22
          Web Apps
        • 19
          Used by top startups
        • 18
          Clean
        • 17
          Easy setup
        • 16
          Sexy
        • 13
          ORM
        • 13
          Convention over configuration
        • 10
          The Django community
        • 10
          Allows for very rapid development with great libraries
        • 7
          King of backend world
        • 7
          Its elegant and practical
        • 7
          Great MVC and templating engine
        • 6
          Have not found anything that it can't do
        • 6
          Cross-Platform
        • 6
          Batteries included
        • 6
          Fast prototyping
        • 6
          Full stack
        • 6
          Mvt
        • 5
          Easy to develop end to end AI Models
        • 5
          Very quick to get something up and running
        • 5
          Easy Structure , useful inbuilt library
        • 4
          Great peformance
        • 4
          Easy to use
        • 4
          Python community
        • 4
          Many libraries
        • 4
          Modular
        • 4
          Easy
        • 3
          Scaffold
        • 3
          Full-Text Search
        • 3
          Map
        • 3
          Zero code burden to change databases
        • 3
          Just the right level of abstraction
        • 2
          Easy to change database manager
        • 1
          Node js
        • 0
          Fastapi
        • 0
          Rails
        CONS OF DJANGO
        • 25
          Underpowered templating
        • 21
          Autoreload restarts whole server
        • 20
          Underpowered ORM
        • 15
          URL dispatcher ignores HTTP method
        • 10
          Internal subcomponents coupling
        • 7
          Not nodejs
        • 7
          Configuration hell
        • 7
          Admin
        • 5
          Not as clean and nice documentation like Laravel
        • 3
          Bloated admin panel included
        • 3
          Not typed
        • 3
          Python
        • 2
          Overwhelming folder structure
        • 2
          InEffective Multithreading

        related Django posts

        Dmitry Mukhin

        Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

        Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

        For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

        However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

        All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

        See more

        Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

        See more