At the moment I only has basic knowledge on Django, to deploy to aws ec2, rds and s3. I’m building iOS app with real time chat functionality, with supabase as backend. I was wondering maybe I should deploy Django instead but the learning curve is websocket and redis. Is working with channel and websocket is a complex story in Django?
#Websocket: is it complicated?
lone glen
silent sparrow
It is not a massive learning curve, but it is very different from HTTP request-response.
whole scarab
Channels is intimidating at the start, but once you pass the initial barrier (understanding how it works) it should be quite simple to work with. I suggest you run a test locally and move from there.
marble surge
WebSockets and Django Channels have a moderate learning curve if you’re new to asynchronous programming and Redis. However, Django Channels simplifies much of the complexity, making it manageable with some practice and good tutorials.
viral hornet
Unfortunately, websockets are one of django's major weaknesses compared to some other backend frameworks. There isn't a quick out-of-the-box solution that just works, so as mentioned, the biggest hurdles are the initial setup and wrapping your head around the technologies involved
but after than it's pretty smooth sailing