14293
Telegram group for Django users. Django is a high-level Python Web framework (djangoproject.com). Rules from @Rules_for_Python apply here too, read them!
In order to get a fit answer you have to understand that you are a problem solver and as long as you don't see the need they are is non need on your level.
Otherwise if you are designing a microservice project with an API first approach where you are dealing with a backend which connects different databases you will definitely see the importance of separation of the backend and frontend code .
Yes, DRF + Next.js works well. Just don't create a global Zustand store in Next.js, because the server shares it between users (like a global variable in Django). Create the store per request instead.
Читать полностью…
https://www.djangoproject.com/weblog/2026/aug/28/django-developers-survey-2026-results/
Читать полностью…
zustand is good
but next.js has server component then client component
can you use global state with zustand in next.js as you use global state with vite?
can you use django rest framework as backend and next.js as frontend?
but what happen in zustand in next.js?
Topic: What’s the actual use of React or Next.js?
Hi everyone :)
I’m pretty comfortable with Django, but on the frontend side I’ve mostly worked with plain JavaScript and AJAX so far. I still haven’t fully understood what problem React and Next.js are actually solving and when it makes sense to use them.
For example, things like changing product quantities, comparing products, managing a shopping cart, placing an order, etc. can all be implemented with plain JS and AJAX, and from my experience, they don’t seem particularly complicated.
So what exactly is the advantage of using React and Next.js instead? At what point does a project become complex enough that using them actually becomes worthwhile?
Or could it be because I work with Django, and since a lot of the logic and processing is handled on the backend, I don’t feel as much need for React/Next.js?
I’ve also tried asking AI about this, but the answers I got mostly came down to “better management of complex projects,” and I still can’t really visualize what kind of complexity they solve that we couldn’t handle properly with plain JS.
I’d really appreciate it if someone could explain it with a real-world, practical example. 🙏
He is asking a package, not client or server.
Seems you are not genuine django developer
Spot on. Auth always looks so straightforward on paper until you're deep in the weeds with token expiries, role permissions, and users forgetting their passwords every 5 minutes. Tbh, it's half the reason I'm glad I sit on the product side these days... I just write the requirements and let the engineers deal with the headache. Kidding. Mostly.
Читать полностью…
Hi! This group is English-only. Please, translate your message into English and delete the non-English message. Or move to a group speaking your language (type "!ol" to see the list). Thank you!
Читать полностью…
Started with backend work years ago and Django clicked for quick, clean projects. Building a couple real apps helped more than tutorials. The market still values people who can ship stuff without overcomplicating the stack.
Читать полностью…
Seems you want server not client. You can use oficial MySQL
Читать полностью…
idk how about free resources dj, but i can recommend u can use supabase services.that's free postgresql db.
Читать полностью…
The issue is most likely related to infrastructure rather than Django or React itself. Common causes include high network latency between GoDaddy and the DigitalOcean server, slow DNS resolution, reverse proxy (Nginx/Apache) configuration, SSL/TLS handshake delays, CORS preflight requests, unoptimized PostgreSQL queries, insufficient Gunicorn workers, or missing caching/compression. Use your browser's Network tab to identify where the delay occurs (DNS, TTFB, SSL, or API response), then optimize that specific component. If the local frontend is fast but the hosted domain is slow, the hosting or network configuration is the most likely cause.
Читать полностью…
You're probably using Django templates with some JS/AJAX, and that works great for most sites. React becomes useful when many parts of the page depend on the same data (cart badge, mini-cart, totals, checkout button). With plain JS you update each one manually and bugs creep in as the page grows. With React you change the state and the UI updates itself.
It's also useful when you want a decoupled setup (DRF as API + Next.js as frontend), which I use. For content sites and simple forms, though, Django templates + JS is simpler and totally fine.
zustand is meant for state management of client side react, it has nothing to do with next or drf.
Читать полностью…
Django is a framework which has simplified a lot of things we have to handle on the backend like request response lifecycle, using an orm query to fetch data from db and handling database tables and data with just classes and objects, etc. likewise react have simplified a lot of things we would have to write and also gives easy reusability. Nextjs goes an extra step where it can be both frontend and backend with same code and it has simplified backend further
Читать полностью…
XAMPP Apache + MariaDB + PHP + Perl
Django runs on Python
Can you see how XAMPP is unsuited for the task at hand? And why one would recommend to simply use MySQL (or MariaDB) instead of using a package of server-side software that mostly consists of irrelevant parts for Django?
Exactly, token expiry and role hierarchies hit you in production. Learned that the hard way on a multi-tenant app
Читать полностью…
Sorry about that! What I meant to say: totally agree, real projects teach way more than tutorials. Auth and permissions are the hard part.
Читать полностью…
Tbh the bit that helped me most was building a couple of boring but real apps end-to-end. Tutorials are fine, but they don’t teach you the awkward bits like auth, permissions, errors, and the mess that comes with actually shipping stuff. Also, getting comfortable reading existing code is a huge one - that’s basically half the job in the real world.
For job-ready stuff, I’d say Django basics, DRF, PostgreSQL, testing, and deployment are the usual suspects. And maybe a bit of system design once you’re past the beginner stage. The market still seems to value people who can ship without turning every ticket into a philosophical debate, which is nice for once 🙂
Hi everyone 👋
I’m currently learning Django and working on improving my backend development skills. I really enjoy Django and I’m trying to build real projects to become a better developer.
I would love to hear from experienced Django developers and seniors here about your journey:
* How did you start your career with Django?
* What skills or topics helped you the most to become job-ready?
* What does the Django job market look like these days?
* If you were starting again as a beginner, what would you focus on?
Any advice, personal experiences, or lessons you’ve learned would be really appreciated. Thanks in advance for taking the time to share your knowledge 🙏
Any MySQL client available for Django 5.2 or later , in xampp MySQL 8 is not available till now
Читать полностью…
Guys any free resources to host django application including db and redis render is now askingfr charges for database service
Читать полностью…
The issue is most likely related to infrastructure rather than Django or React itself. Common causes include high network latency between GoDaddy and the DigitalOcean server, slow DNS resolution, reverse proxy (Nginx/Apache) configuration, SSL/TLS handshake delays, CORS preflight requests, unoptimized PostgreSQL queries, insufficient Gunicorn workers, or missing caching/compression. Use your browser's Network tab to identify where the delay occurs (DNS, TTFB, SSL, or API response), then optimize that specific component. If the local frontend is fast but the hosted domain is slow, the hosting or network configuration is the most likely cause.
Читать полностью…
Check the network tab of developers tools of your browser
Читать полностью…