I want to make a site for playing chess, is django suitable for the backend?

Question

Django

My first project, I want to make a website where two people can play chess . I

plan to register, integrate with VK (like calling authorized users from friends to a match), in-game chat (optional), a general chat list where calls to a match

Front and back are on me

The goal of all this is to acquire backender skills as basic ones, so the front will also be on me, well, a little front will not hurt me, it seems to me.
Time for all this is 2.5 months

. for large projects), I have no idea about the Front yet, but I don’t know js at all, I would like it without it, tell me how easier it is with it (front)

The essence of the question: how does it all look adequate / inadequate, real or not; django will go for such a project; What would be your advice to me as a beginner?

I will be very glad to all the answers, any criticism, and advice from experienced developers and not only

Answer 1

django will do.
With it in the kit you will receive an admin panel, registration, authorization.
It's not hard to find good ready-made modules for django with websocket chat.
There are ready-made dzhang OAuth modules and all sorts of integrations into social networks.

Answer 2

Sounds very inadequate. Forgivable to the newcomer... probably.
Django is a Python framework. Sharp (C#) is a language (correct me if anyone knows such a frame). The difference is like between the sun and goats in the nose.
If we take only the need for a database + authorization, I would recommend Flask + libraries like Flask-Login (also a Python framework). The speed of calculations is not needed, you didn’t write what you are going to do with AI. So it will do.
But at the expense of 2.5 months ... Well, if you are genius enough, then you will succeed. Otherwise, with no knowledge, in such a short time you are unlikely to come up with something that works and is not propped up with crutches from a toaster and a glass.
Yes, and you most likely need web sockets. Or write constant requests to update the data for the board. This is not counting the development of the muzzle itself (board).