Channels vs serverless: how much they are alike

[Виталик Абеткин]

From what I know serverless architectures use message queues and distribute tasks that handle various events to workers

pretty much in the same way django channels do. How much they are really alike? For instance, let's take openwhisk.org implementation

[Andrew Godwin]

Channels' message queue is designed for a much lower latency than most "serverless" solutions, which are more often for non-interactive processing. There's a whole host of other differences too, around design, deployment, etc. that are all tradeoffs; at some point, a lot of distributed systems come down to message passing and separate tasks (e.g. SOA infrastructures) that it's hard to talk about these things without a clearer definition of what "serverless" actually means.

Andrew

On Sun, Mar 5, 2017 at 3:00 PM, Виталик Абеткин <abv...@gmail.com> wrote:

From what I know serverless architectures use message queues and distribute tasks that handle various events to workers

pretty much in the same way django channels do. How much they are really alike? For instance, let's take openwhisk.org implementation

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b9250070-386f-46e0-92d5-42809f6e6a3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.