Don't move fast to another stack.⚠️

Read this story from Lahiru Hewawasam on Medium: Link

Deploy web applications which is made with django on the Render.
https://testdriven.io/blog/django-render/

In some cases django devs have one problem with migrations files, so i think the guy who is first met with this issue is gonna delete all of migrations and data in DB. if he does this in the production he will might lost all real data 😰🥴🥶.
Ok WHAT SHOULD IT DO ???
Django has — fake flag which is written with migrate command together like this: python manage.py migrate —fake
It tells to Django that migrations have already applied and not need to run it(DON'T RUN IT).
Actually it creates a row in django_migrations table but not run in the SQL to change table structure.
In one another case if you have multiple migrations file you can delete all of them and use above flag(argument).

Improving API Performance
More

🔥 I absolutely recommended reading this article to learn more about object serializing way and you realize that which way is the best to serialize in short time.

https://hakibenita.com/django-rest-framework-slow

Architectures
More

Devops haqida bu saytdagi🍊 maqolalar juda yaxshi yozilyapti uzbek tilida 😍

Github actions haqida: https://devops-journey.uz/guides/ci-cd/github-actions-ci-cd.en-UZ

Backend Dasturchilar uchun 10 ta eng muhim operatsion tizim konseptsiyasi.

https://masteringbackend.com/posts/the-10-operating-system-concepts-for-backend-developers

⏩⏩ Nima uchun Django loyihani serverga joylayotganimizda gunicorn servisidan foydalanamiz ?, Django runserver dan foydalanish mumkinku !?

Bu yangi dasturchilar orasida juda ko'p so'ralgan savol

Bu yerda mening tushuncham:👇

⛔️ Djangoning runserveri Single-Thread:

Ko'p qatorli avtomagistraldan farqli o'laroq, runserver - bu bitta qatorli yo'l ga o'xshaydi. U bir vaqtning o'zida faqat birgina so'rovni tutib(handle) qolishi mumkin, bir vaqtning o'zida bir nechta so'rovlar kelganda navbatlarning paydo bo'lishiga olib keladi. Bu userlar yuqori trafik ostida qolib, javob olish vaqtlari sekinlashishiga olib keladi.

✅ Enter Gunicorn: The Concurrency Hero 💪

Gunicorn production muhitida:

✅ Concurrent Processing: Gunicorn ishchi processlarini yaratadi, har biri mini-django app sifatida ishlaydi. So'rovlar yetib kelgan vaqtda, Gunicorn ishchilarni(workers) bo'lib tashlaydi, processlarga parallel ravishda ishlashga imkon beradi. Va bu sezilari darajada performance ni oshishiga tasir qiladi, ayniqsa og'ir trafik ostidagilar uchun.

✅ Scalability: Gunicorn da trafik talablaringizga mos worker processlarning sonini sozlab quyish mumkin.Bu avtomagistrallarga eng tirband bo'lgan vaqtda qo'shimcha yo'llar qo'shishga o'xshaydi

✅ Production-Ready Features: Gunicorn real loyihalarning deployment jarayoni uchun muhim hususiyatlarni taqdim qiladi, ya'ni quyidahilar:

🔹 Pre-forking - so'rovlarni samarali handle qilish uchun worker proccesslarni qayta ishlatish.

🔹 Ilovani restart qilmasdan uning code larni muammosiz o'zgartirish uchun juda zo'r Reloading.

🔹 Timeouts va workerlarni samarali monitoring qilish scaling uchun.

🔹 Yuqori darajadagi loggin va errorlarni handle qilish kuzatishni yaxshilash uchun.

Gunicorndan foydalangan holatda, siz Django loyihangizni samarali scale qila olasiz, so'rovlarni parallel ravishda handle qilish, va foydalanuvchiga muammosiz yetkazib berish – hatto yuqori o'lchamdagi traffic bo'lgan taqdirda ham.

#savol
Access tokenni yaroqlilik muddatini 2 3 yil qilsam ham boladimi. 😢

javob:
haa bo'ladi, lekin bu holatda havfsizlikni o'ylamasangiz ham bo'ladi chunki agar hujum qilishmoqchi bo'lsa 1 2 kunda dasturizni qo'lga olishi mumkin. token dan foydalanmasangiz ham bo'ladi😁 agar 2 3 yil qilmoqchi bo'lsangiz chunki foydasi tegmaydi baribir.

Backend dasturchi bilishi kerak bo'lgan eng muhim 'qobiliyat' nima deb o'ylaysiz ?

Javoblarni komentariyada qoldiring, men uzimnikini kun yakunida qoldiraman.

Men uchun eng muhim part bu Database Structurasi ya'ni uni qurish, Design qilish.

Chunki bu qismni skip qilib ketish oqibatida kelajakda ko'p disadvantage tomonlarini kurishimiz mumkin.

1. Kod Trash ga aylanishi aniq I think so.

2. Ma'lumotlarni optimal tarzda database ga saqlash, olish, o'chirish, yangilash(CRUD) ni tezligini bir necha barobarga oshiradi.

3. Ortiqcha keraksiz querylarni yozishdan qutilish.

Design Tayyor boo'lgandan so'ng Mazza qilib api chiqarishga o'tsez bo'ladi 😂

Tepada yangi boshlayotgan loyihamizni Database Design ni, bugungi qilgan ishim shu bo'ldi🤓

Kamchiliklar bo'lsa yoki qo'shimcha qo'shmoqchi bo'lsangiz komentariyada fikringizni qoldiring 👇🏻

Bitta Django Loyihada qanday qilib bir nechta Database lardan foydalanish mumkin ?

#edited

pre-commit larni ishlatgan holda kodizni bir nechta Tekshiruvlardan o'tkazib toza 🧹, missed xatoliklardan fix qilib 🥺, refactoring qilish 🥶 va black,flake8,isort larni ishlatib vanihoyat yaratilmagan migratsiyalar qolib ketgan bo'lsa😢 ularni ham tekshirib Testlardan🧪 o'tkazib, coverage ni ham aniqlab ko'rgandan so'ng✅ commit bo'lganini ko'rsangiz mazza qivorasiz 😎, ishonavering 😁

pre-commit haqida nimalar bilasiz, batafsil post qilishimni hohlaysizmi ?

leave your thoughts in the comments 👇🏻