gqtx
django-channels
Our great sponsors
gqtx | django-channels | |
---|---|---|
6 | 14 | |
447 | 5,906 | |
- | 1.3% | |
0.0 | 5.5 | |
3 months ago | 20 days ago | |
TypeScript | Python | |
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gqtx
-
Replacing Nexus
My favorites are Pothos and gqtx. In terms of documentation and adoption Pothos definitely wins over gqtx. You might also want to check out the "I'm struggling to find proper Graphql Stack" Reddit thread.
-
Solving the double (quintuple) declaration Problem in GraphQL Applications
By now you get a lot of typesafety without the need to write any types manually or having to generate them on the on the server by using https://github.com/sikanhe/gqtx
-
What do you think about nexus? I'm new at this and wondering if I should use it in my project.
There are multiple ways available of constructing a graphql schema. Usually, you can break down those into "SDL" First and "Code" First. A simple example of a Code First approach is the programmatic graphql.js API using `new GraphQLObjectType`. You define your schema with code. In an SDL First approach, you write your schema in the GraphQL SDL (as text) and define a resolver map. You can find some examples over here: https://graphql.org/graphql-js/constructing-types/ A lot of tooling has emerged of those two methods of building GraphQL schemas and you usually have to choose whether you wanna stick to Code First or SDL First. Tools like gqtx (https://github.com/sikanhe/gqtx), giraphql (https://github.com/hayes/giraphql), and nexus (https://github.com/graphql-nexus/nexus) are built around the Code First approach and improve the developer experience over the programmatic API form graphql.js by providing a more type-safe API when utilizing TypeScript. They ultimately all do the same, with slightly (more or less opinionated) different APIs. On the other hand tooling for SDL has also evolved. graphql-tools provides a more advanced interface over how you define the resolvers map and a lot of utilities for constructing your schema from SDL/resolver map partials distributed across different files (https://www.graphql-tools.com/docs/generate-schema/). Together, with graphql-codegen resolver type generation (https://www.graphql-code-generator.com/docs/plugins/typescript-resolvers) you can bring this to the next level if you are working with TypeScript and generate fully typed resolvers from the GraphQL SDL. You have to find out for yourself which approach is best suited for you. I have been using both on different projects and they both have benefits and trade-offs. My opinion is mostly based on the TypeScript developer experience. Code First seems to be the better pick for me if you have lots of computed fields that cannot be mapped 1:1 to the data sources, where you would have to add a lot of type resolver mappings configuration for codegen. With SDL I like that I have the feeling that I can write the schema faster and less clumsy, and the SDL is immediately readable. On Code First you, however, can still generate an SDL file from the coding schema. Maybe there is a niche open for an approach that combines Code and SDL First approaches. We will have to see what the future brings. Here are some more articles/threads regarding the topic: https://www.prisma.io/blog/the-problems-of-schema-first-graphql-development-x1mn4cb0tyl3 https://www.reddit.com/r/graphql/comments/fpkx7a/codefirst\_vs\_schemafirst\_development/ https://blog.logrocket.com/code-first-vs-schema-first-development-graphql/ Also, note that most GraphQL server/transports do or should not care about the way you construct your schema. E.g. the apollo-server docs show you only an SDL first way of constructing the schema (https://www.apollographql.com/docs/apollo-server/schema/schema/), but it is also possible to provide a schema instance(https://www.apollographql.com/docs/apollo-server/api/apollo-server/#schema). apollo-server defaults to advocating creating a schema with SDL (by using an old graphql-tools@4 version under the hood).
Tools like gqtx (https://github.com/sikanhe/gqtx), giraphql (https://github.com/hayes/giraphql), and nexus (https://github.com/graphql-nexus/nexus) are built around the Code First approach and improve the developer experience over the programmatic API form graphql.js by providing a more type-safe API when utilizing TypeScript. They ultimately all do the same, with slightly (more or less opinionated) different APIs.
-
Need guidance on apollo subscription fallback
If I can give you an additional tip: Think twice whether you actually need apollo-server. All you need is a way of constructing a schema, which you can either do with the graphql.js programmatic API, graphql-tools (https://www.graphql-tools.com/docs/generate-schema/), or type-safe code first schema builders such as https://giraphql.com/ or https://github.com/sikanhe/gqtx
-
What are your thoughts on Next/Apollo/Prisma stack? Should I use it for my project (see details in the description)? Can you share some advice?
You will also have to figure out which schema generation flow suits you best. E.g. you can use the programatic API from graphql-js, makeExecutableSchema from graphql-tools https://www.graphql-tools.com/docs/generate-schema/ or code schema builders like https://github.com/sikanhe/gqtx or https://github.com/hayes/giraphql
django-channels
- Django. Работа через WebSocket. Библиотека Channels
-
How to implement a chat room using Jquery/PHP?
WebSockets or MQTT. If you’re open to Python and Django as a framework, check out Django Channels.
-
Sending events or notifications from Django
Use Django channels package. I'm not very convinced for these reasons:
-
Sending data to django channels groups via django views
github issue
- Show HN: WAPM – WebAssembly Package Manager
-
Recommendations for a clean Github repository to use as an example for a new Python project
One program I sorta like is channels. You may have some luck searching for python example repositories (IIRC there is at least one project like this, with the structure and explaining what each stuff does, give preference to more recent projects as packaging is something that went through a lot of changes in the recent years).
- Solving the double (quintuple) declaration Problem in GraphQL Applications
-
Why and how we ditched Django Channels to build a scalable chat backend
This is my first post, and I am sharing the experience of using Django Channels for a couple of our products, which are both live, one(legacy product) still running django channels and another deployed at AWS API Gateway using Websockets API.
What are some alternatives?
django-socketio - WebSockets for Django
Flask-SocketIO - Socket.IO integration for Flask applications.
Crossbar - Crossbar.io - WAMP application router
websockets - Library for building WebSocket servers and clients in Python
pusher django photo feed - A real-time photo feed using Django and Pusher
AutobahnPython - WebSocket and WAMP in Python for Twisted and asyncio
WebSocket-for-Python - [Project on Hiatus] WebSocket client and server library for Python 2 and 3 as well as PyPy (ws4py 0.5.1)
uvicorn - An ASGI web server, for Python. 🦄
DjangoChannelsGraphqlWs - Django Channels based WebSocket GraphQL server with Graphene-like subscriptions
pothos - Pothos GraphQL is library for creating GraphQL schemas in typescript using a strongly typed code first approach
mercurius-typescript - TypeScript usage examples and "mercurius-codegen" for Mercurius
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]