django-channels VS TypeGraphQL

Channels Medium Article

WebSockets or MQTT. If you’re open to Python and Django as a framework, check out Django Channels.

Creating a PWA is not like playing a card that wins the game. Moreover, users do not yet know the potential or do not know that they can be installed so they have a bit of a hard time catching on. At the moment I use Django + HTMX + AlpineJS to build my applications. This stack allows you to use WebSockets, but HTMX is not yet very mature in this respect. If you aim to create something complex on the user experience side, I have used the Django (+ Django rest framework) + React stack for years. It's good but it takes time both for creating things and to master it. Maybe you want to check out Django Channels too https://github.com/django/channels

Use Django channels package. I'm not very convinced for these reasons:

github issue

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).

Extra background information: * https://stackoverflow.com/a/49043121/1842286 * https://stackoverflow.com/questions/62199335/django-session-is-not-being-persisted-and-cookie-is-not-being-set-when-using-dja * https://github.com/django/channels/issues/1425 * https://github.com/django/channels/issues/1402 * https://github.com/django/channels/issues/1096

In this tutorial, we're building a simple application which uses Cerbos inside of a GraphQL server. The server is written in typescript and uses type-graphql to create the schema and resolvers, and TypeDI to handle dependency injection.

Using decorators required setting an --experimentalDecorators experimental compiler flag. Several popular TypeScript libraries, such as type-graphql and inversify, rely on this implementation.

TypeGraphQL

Have you tried TypeGraphQL v2 (it's in beta). Some in this thread have reported success with it.

When moving away from Apollo Server, and you're looking for a replacement built with JavaScript or TypeScript, let me give you some options. If you want to keep building your GraphQL API schema first, you might want to consider Mercurius (which relies on Fastify) or GraphQL Yoga. If you're going to build your GraphQL API code or resolver first, have a look at TypeGraphQL or Nexus. Alternatively, there are great GraphQL-as-a-Service solutions such as StepZen in case you no longer want to build, maintain and host your own GraphQL API.

There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.

I've used tools (e.g. TypeGraphQL) in the past, and for smaller schemas I've just manually written the schema.

I'll be honest and say I don't think python is the right language to implement graphql. It's possible of course and if you're looking for a graphene tutorial, I'm sure you can find one (and I'll help you evaluate one, if you'd like). I'd personally go with node.js, typescript, and typegraphql.

Foal's dependencies have been updated so as to support the latest version of TypeGraphQL.