HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
django
channels
Python2015–2022
django / channels

channels

Developer-friendly asynchrony for Django

Developer ToolsWeb Development
Explore on GitHubRead Hacker News discussions
10Distinct people
10Mentions
0Explicit recommenders
6.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Developer-friendly asynchrony for Django

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2015-09-24 08:42:49 UTC to 2022-03-02 19:40:24 UTC.

02462015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC633
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

10 sources
djstein·Aug 14, 2021
Current stack for creating easy to use GraphQL APIs + Frontend Integration: - Django 3 backed with a Postgres database (standard stuff) [0] - Add Graphene to enable Relay [1] - Setup a fresh TypeScript based NextJS project [2] - Add graphql-code-generator with a few plugins, mainly the graphql-request one [3] - THE MAGIC: Generate your sdk by pointing graphql-codegen at your Django GraphQL schema! - Add react-query, use the newly generated graphql-request client [4] From here you've enabled the best of frontend technologies (NextJS, react-query) with a fully typed SDK generated by your familiar Python/Django bindings. You can then move forward to add GraphQL based WebSockets via django-channels [5] + django-channels-graphql-ws [6] that update your existing react-query caches. Combine this with background Celery workers that make push to d
Read the rest
jango-channels via Redis and you've got a a UI that auto updates based on background tasks as well. [0] https://www.djangoproject.com [1] https://docs.graphene-python.org/projects/django/en/latest/ [2] http://nextjs.org/ [3] https://www.graphql-code-generator.com [4] https://react-query.tanstack.com [5] https://github.com/django/channels [6] https://github.com/datadvance/DjangoChannelsGraphqlWs [Edit] Line formatting
In Solving the double (quintuple) declaration Problem in GraphQL Applications
tedmiston·Jul 1, 2016
Kind of. 48 contributors total (Yes, Andrew is doing most) - https://github.com/andrewgodwin/channels/graphs/contributors It sounds like it wasn't decided to keep 3rd party as much as decided not to not combine yet: > The feedback I got during the proposal process for putting Channels into Django 1.10 (it did not get in before the deadline, but will still be developed as an external app with 1.10) was valuable; some of the more recent changes and work, such as backpressure and the local-and-remote Redis backend, are based on feedback from that process, and I imagine more tweaks will emerge as more things get deployed on Channels. https://www.aeracode.org/2016/6/16/philosophy-channels/ You can still use Channels today in 1.8–1.10. https://blog.heroku.com/in_deep_with_django_channels_the_fut... This project is very much in the spotlight, wa
Read the rest
s heavily discussed at PyCon, etc. I don't think it's going anywhere.
In Rails 5.0: Action Cable, API mode, and more

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.