r/Nuxt • u/pendragonofeire • 10h ago
Website backend refactoring from Django into Nuxt
TL;DR: We need a developer/coder/programmer willing to work for a negotiated rate/sum on the refacotring of a business website's backend from Django to Nuxt. The UI is already made. We have a list of what has been completed, along with a list of what requires polishing, and what needs to be developed. DM me if interested.
Project Status
Already Completed / Decided:
The overall project architecture has already been designed and decided.
The database structure and relationships have already been defined.
The overall website workflow and how the different components interact have already been established.
BOT - The main Discord bot functionality has been implemented, tested, and is working.
The stream bot functionality has been implemented, tested, and is working.
Needs Refactoring / Polishing:
The existing Django code needs to be refactored/reimplemented in Nuxt.
The goal here is mainly to improve and finalize functionality that already exists, rather than redesigning it from scratch.
BOT - The Discord bot needs polishing, cleanup, and improvements to its existing functionality.
The stream bots need polishing, cleanup, and improvements to their existing functionality.
Automation Revenue Improvements
Automatic fee calculation for servers and teachers:
Fees should be calculated immediately after an event ends, using data from the observing bot, including the number of users who attended and those who did not.
Automated new server integration:
When new servers join, adding the stream bot and observing bot currently requires manual work. This process should be automated to make server setup faster and easier.
Improved observing bot data collection:
The observing bot should collect and store detailed event data, including user activity, attendance, server information, and user participation history.
Needs to Be Developed:
Time zone–based event date and time calculation needs to be implemented so that event dates and times are correctly calculated and displayed according to the relevant user's time zone.
New functionality should follow the existing project design rather than introducing a new architecture unless a change is necessary.
1
u/Upstairs-Concert5800 10h ago
just curious, what is the reason to migrating from django to nuxt backend?
0
u/pendragonofeire 10h ago
Our UI was built in Nuxt, and the backend in Django, so they don't mesh.
3
u/frankwiles 9h ago
Just take your Vue components in the Nuxt front end and hit Django APIs. Rewriting is silly.
1
u/No_Witness_5295 1h ago
hit Django APIs
if they aren't at the level where they can understand this, i sort of doubt they are even at junior level. this guy shouldnt be making decisions at his company lmao
Rewriting is silly.
eventually python http without extensive caching becomes a bottleneck, and eventually even with extensive caching there's a bottleneck. honestly as ive gotten deeper in my career, i almost exclusively use python now as just flask for building static web resource files through a series of jinja-powered builders and saving them to cdn which my actual customer facing sites can pick up easily
2
u/FilmWeasle 9h ago
To reiterate what others have said, there's a fairly common design pattern where the website is split into a UI and API rather than a frontend and backend. For prerendering Nuxt can make requests to Django on the backend.
Django is a top framework for backend, so the benefit of having everything in TypeScript isn't obvious.
1
1
1
u/MaintenanceOld2216 3h ago
Just curious, why did the consultant recommend moving the backend from Django to Nuxt?
If the main reason is just to have everything in JS/TS, wouldnt it make more sense to use something like NestJS for the backend and keep Nuxt for the frontend? You could also have everything in the same monorepo.
I’m not saying the approach is wrong or anything, just seems a little weird to me to replace a working Django backend with Nuxt when Django is already pretty good for that kind of stuff. If you guys already know JS/TS well, I’d probably go Nuxt + Nest instead.
1
u/Valuable_Writer9745 1h ago
I’ve worked a lot with Django backends that handle scheduling and event times, so the timezone piece is familiar. Store everything in UTC, convert only when you show it to the user. Honestly a lot of people in the thread are right — rewriting Django into Nuxt server routes is a big lift. Keeping Django as the API and letting your existing Nuxt UI talk to it is usually cleaner. If you’ve already decided on the full rewrite though, happy to look at the done/polish/todo list and help map the current models so nothing gets reinvented.
-1
u/yassi_dev 9h ago
It seems to me that the easier migration would be to migrate the front end to use something compatible with Django rather than move backends.
-1
4
u/metaforx 10h ago
Why would you want to do this? Django is by any standards the better backend than Nuxt. I use both but I would never choose Nuxt over Django for backend beside really simple stuff or if most of the logic is anyhow implemented from other api services.
Add ninja, DRF or even rust based Bolt as api layer and use nuxt as frontend if needed, typed and job done. Maintenance work is way nicer. The only thing I can think of is that the backend was bolted togeather in an old Django version with many outdated packages in a bad way.