django-channels VS serverless-graphql

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

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless