Forwarded from Botir Ziyatov
Bu men ko‘rgan eng tez rivojlanayotgan veb-sayt!
Bu sayt 2025 yil aprel oyida ochilgan:
Iyul oyida - 49 ming tashrif
Avgust oyida - 290 million tashrif!
Sayt qanday ishlaydi:
Bu saytda dunyo xaritasi keltirilgan, u yerda xarita ustiga rasm chizish va boshqalarning chizgan rasmlarini ham ko‘rish mumkin.
Odamlar o‘z mamlakatlarida, shaharlarida turli rasmlar, bayroqlar, yozuvlar chizishyapti. Ba'zilari birgalikda katta asarlar chizmoqda.
Hamma qatnasha oladigan ishlar tezroq mashhur bo‘ladi.
@botirziyatov
Bu sayt 2025 yil aprel oyida ochilgan:
Iyul oyida - 49 ming tashrif
Avgust oyida - 290 million tashrif!
Sayt qanday ishlaydi:
Bu saytda dunyo xaritasi keltirilgan, u yerda xarita ustiga rasm chizish va boshqalarning chizgan rasmlarini ham ko‘rish mumkin.
Odamlar o‘z mamlakatlarida, shaharlarida turli rasmlar, bayroqlar, yozuvlar chizishyapti. Ba'zilari birgalikda katta asarlar chizmoqda.
Hamma qatnasha oladigan ishlar tezroq mashhur bo‘ladi.
@botirziyatov
Forwarded from Otabek Kholmirzaev 💻
Agar siz (1 oy ichida) System Design da yaxshi bo‘lishni istasangiz, mana bu case study-larni o‘rganing:
1. How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines
2. How Google Ads Was Able to Support 4.77 Billion Users With a SQL Database
3. How Meta Achieves 99.99999999% Cache Consistency
4. Real Time Gaming Leaderboard Architecture
5. How Uber Finds Nearby Drivers at 1 Million Requests per Second
6. How to Scale an App to 10 Million Users on AWS
7. How Cloudflare Supports 55 Million Requests per Second With 15 Postgres Clusters
8. How Slack Works
9. How YouTube Was Able to Support 2.49 Billion Users With MySQL
10. Pastebin Architecture
11. How Stripe Prevents Double Payment Using Idempotent API
12. How Uber Computes ETA at Half a Million Requests per Second
13. Redis Use Cases
14. How Amazon S3 Achieves 99.999999999% Durability
Muallif: Neo Kim
———————————————
@Otabek_Kholmirzaev
1. How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines
2. How Google Ads Was Able to Support 4.77 Billion Users With a SQL Database
3. How Meta Achieves 99.99999999% Cache Consistency
4. Real Time Gaming Leaderboard Architecture
5. How Uber Finds Nearby Drivers at 1 Million Requests per Second
6. How to Scale an App to 10 Million Users on AWS
7. How Cloudflare Supports 55 Million Requests per Second With 15 Postgres Clusters
8. How Slack Works
9. How YouTube Was Able to Support 2.49 Billion Users With MySQL
10. Pastebin Architecture
11. How Stripe Prevents Double Payment Using Idempotent API
12. How Uber Computes ETA at Half a Million Requests per Second
13. Redis Use Cases
14. How Amazon S3 Achieves 99.999999999% Durability
Muallif: Neo Kim
———————————————
@Otabek_Kholmirzaev
Forwarded from Otabek Kholmirzaev 💻
GitHub
GitHub - jwasham/coding-interview-university: A complete computer science study plan to become a software engineer.
A complete computer science study plan to become a software engineer. - jwasham/coding-interview-university
Texnik intervyular → QIYIN.
5 xil intervyu turi uchun → 5 ta bepul resurs:
→ Coding Interview:
1. Coding Interview University
2. Grind 75 Practice Questions
3. Awesome Leetcode Resources
4. Neetcode App and Youtube
5. The Tech Interview Handbook
→ System Design Interview:
6. Awesome System Design Resources
7. System Design 101 (76k stars)
8. System Design Basics Playlist on Youtube
9. System Design Github Repo (by Neo Kim)
10. The System Design Roadmap (by roadmap.sh)
→ Object Oriented Design Interview:
11. Awesome Design Patterns (44k stars)
12. Design Patterns with Visuals
13. Awesome Low-Level Design
14. Design Patterns Youtube Playlist
15. System Design Primer (259k stars)
→ Frontend Interview:
16. The Front-End Interview Handbook (by Yangshun Tay)
17. Javascript Visualized Series
18. BigFrontend for Practice Questions by Companies
19. Front-End Developer Interview Questions (61k stars)
20. Great Frontend to Plan and Practice (aff.)
→ Behavioral Interview:
21. Awesome Behavioral Interviews
22. The Behavioral Interview Youtube Playlist
23. The STAR methodology
24. Behavioral Questions with Example Answers
25. Interview Questions by Company
Muallif: Alexandre Zajac
→ @Otabek_Kholmirzaev
5 xil intervyu turi uchun → 5 ta bepul resurs:
→ Coding Interview:
1. Coding Interview University
2. Grind 75 Practice Questions
3. Awesome Leetcode Resources
4. Neetcode App and Youtube
5. The Tech Interview Handbook
→ System Design Interview:
6. Awesome System Design Resources
7. System Design 101 (76k stars)
8. System Design Basics Playlist on Youtube
9. System Design Github Repo (by Neo Kim)
10. The System Design Roadmap (by roadmap.sh)
→ Object Oriented Design Interview:
11. Awesome Design Patterns (44k stars)
12. Design Patterns with Visuals
13. Awesome Low-Level Design
14. Design Patterns Youtube Playlist
15. System Design Primer (259k stars)
→ Frontend Interview:
16. The Front-End Interview Handbook (by Yangshun Tay)
17. Javascript Visualized Series
18. BigFrontend for Practice Questions by Companies
19. Front-End Developer Interview Questions (61k stars)
20. Great Frontend to Plan and Practice (aff.)
→ Behavioral Interview:
21. Awesome Behavioral Interviews
22. The Behavioral Interview Youtube Playlist
23. The STAR methodology
24. Behavioral Questions with Example Answers
25. Interview Questions by Company
Muallif: Alexandre Zajac
→ @Otabek_Kholmirzaev
👍1
Free Hosting Sites.
1. General Free Hosting Platforms
1. http://github.io
2. http://netlify.com
3. http://vercel.com
4. http://surge.sh
5. http://render.com
6. http://cloudflare.com/pages
7. http://000webhost.com
8. http://infinityfree.net
9. http://freehosting.com
10. http://awardspace.com
2. Free Hosting for Static Websites
11. http://pages.github.com
12. http://sites.google.com
13. http://firebase.google.com
14. http://glitch.com
15. http://neocities.org
16. http://1mb.site
17. http://codeberg.org
18. http://docusaurus.io
19. http://fleek.co
20. http://ipfs.io
3. Free Hosting for Dynamic Websites
21. http://replit.com
22. http://heroku.com
23. http://railway.app
24. http://pythonanywhere.com
25. http://clever-cloud.com
26. http://freeflaskhosting.com
27. http://fly.io
28. http://glitch.me
29. http://cyb.ai
30. http://openshift.com
4. Free Hosting for WordPress
31. http://wordpress.com
32. http://infinityfree.net/wordpress-host…
33. http://x10hosting.com
34. http://biz.nf
35. http://freehostia.com
36. http://byethost.com
37. http://wopop.com
38. http://awardspace.com/wordpress-host…
39. http://pantheon.io
40. http://webfreehosting.net
5. Free Hosting for Node.js Apps
41. http://glitch.com
42. http://render.com
43. http://railway.app
44. http://heroku.com
45. http://vercel.com
46. http://kinsta.com
47. http://clever-cloud.com
48. http://fly.io
49. http://stormkit.io
50. http://deno.com
1. General Free Hosting Platforms
1. http://github.io
2. http://netlify.com
3. http://vercel.com
4. http://surge.sh
5. http://render.com
6. http://cloudflare.com/pages
7. http://000webhost.com
8. http://infinityfree.net
9. http://freehosting.com
10. http://awardspace.com
2. Free Hosting for Static Websites
11. http://pages.github.com
12. http://sites.google.com
13. http://firebase.google.com
14. http://glitch.com
15. http://neocities.org
16. http://1mb.site
17. http://codeberg.org
18. http://docusaurus.io
19. http://fleek.co
20. http://ipfs.io
3. Free Hosting for Dynamic Websites
21. http://replit.com
22. http://heroku.com
23. http://railway.app
24. http://pythonanywhere.com
25. http://clever-cloud.com
26. http://freeflaskhosting.com
27. http://fly.io
28. http://glitch.me
29. http://cyb.ai
30. http://openshift.com
4. Free Hosting for WordPress
31. http://wordpress.com
32. http://infinityfree.net/wordpress-host…
33. http://x10hosting.com
34. http://biz.nf
35. http://freehostia.com
36. http://byethost.com
37. http://wopop.com
38. http://awardspace.com/wordpress-host…
39. http://pantheon.io
40. http://webfreehosting.net
5. Free Hosting for Node.js Apps
41. http://glitch.com
42. http://render.com
43. http://railway.app
44. http://heroku.com
45. http://vercel.com
46. http://kinsta.com
47. http://clever-cloud.com
48. http://fly.io
49. http://stormkit.io
50. http://deno.com
Netlify
Push your ideas to the web | Netlify
Create with AI or code, deploy instantly on production infrastructure. One platform to build and ship.
Forwarded from @Rustam-Z⚡️
Arizalar qabul qilish boshlandi! Do'stlaringiz bilan ham ulashing!
🇺🇿 O'zbekistonda bo'lsangiz ham ariza topshirishingiz va taklif olishingiz mumkin! Interview'larni o'tsangiz bo'ldi, sizga viza bilan ham yordam beriladi.
Asosiy Talablar:
• Kompyuter fanlari yoki tegishli texnik sohada Bakalavr/Magistr/PhD dasturida o'qish.
• Kamida bitta umumiy dasturlash tilida tajriba (Python, JS, C++, Java).
• Data structures and algorithms.
• Ingliz tilini bilish (aloqa uchun talab qilinadi).
• Bu yerda batafsil: google.com/about/careers...
Agar siz barcha bosqichlaridan muvaffaqiyatli o‘tsangiz, Google'ning London 🇬🇧, Shveytsariya🇨🇭, Germaniya 🇩🇪 yoki Polshadagi 🇵🇱 ofislarida ishlash imkoniyatiga ega bo‘lasiz.
Ochiq ish o‘rinlariga link'lar jadvali: docs.google.com/spreadsheets/d/1Fks3mHptIwIY7hvp7BzmvIJ3wHWM6N9KIjWvAKJAT0g/edit?usp=sharing
Ochiq ish o‘rinlari: google.com/about/careers/...
FAQ sahifasi (muddatlar, talablar, vizalar): google.com/about/careers/applications/stories/google-internship-faqs/
‼️ Deadline: 24 October
@cracking_maang
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from @Rustam-Z⚡️
1 year FAANG Interview Preparation ROADMAP
This is what I did when I started preparing for interviews at big tech companies. It helped me land interviews at Meta, Bloomberg, and Google while studying at a university in Uzbekistan. Prerequisite: learn programming.
LINK: https://rustam-z.notion.site/Cracking-MAANG-My-Interview-Preparation-Roadmap-17e1ece53065800fae2cca024f557162
Share it with someone who needs to see this.
🔘 Resources to learn basics of algos, and resources to start practicing with 0 knowledge.
🔘 Questions to ask before solving a problem. MUST CHECK.
🔘 Top patterns and concepts to learn.
⸻
🇺🇿👇
1 yillik Algoritmlarni o'rganish va FAANG intervyusiga tayyorgarlik ROADMAP
O‘zim yasagan roadmap, va universitet vaqtlari o‘qigan resurslarim bilan ulashyapman. Bu bilan Meta, Bloomberg va Google kompaniyalardan suhbatlar o‘tganman.
LINK: https://rustam-z.notion.site/Cracking-MAANG-My-Interview-Preparation-Roadmap-17e1ece53065800fae2cca024f557162
O‘zingizga saqlab qo'ying va boshqalar bilan ulashing 👍
@cracking_maang | www.rustamz.com
This is what I did when I started preparing for interviews at big tech companies. It helped me land interviews at Meta, Bloomberg, and Google while studying at a university in Uzbekistan. Prerequisite: learn programming.
LINK: https://rustam-z.notion.site/Cracking-MAANG-My-Interview-Preparation-Roadmap-17e1ece53065800fae2cca024f557162
Share it with someone who needs to see this.
⸻
🇺🇿👇
1 yillik Algoritmlarni o'rganish va FAANG intervyusiga tayyorgarlik ROADMAP
O‘zim yasagan roadmap, va universitet vaqtlari o‘qigan resurslarim bilan ulashyapman. Bu bilan Meta, Bloomberg va Google kompaniyalardan suhbatlar o‘tganman.
LINK: https://rustam-z.notion.site/Cracking-MAANG-My-Interview-Preparation-Roadmap-17e1ece53065800fae2cca024f557162
O‘zingizga saqlab qo'ying va boshqalar bilan ulashing 👍
@cracking_maang | www.rustamz.com
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from Jakhongir Rakhmonov - IT
Bu narsani har bir backend dasturchisi bilishi shart
Backendni jiddiy o‘rganaman degan dasturchi albatta Distributed System lar haqida o‘rganishi kerak. Chunki minglab, millionlab foydalanuvchilar ishlatadigan sistemalar distributed bo‘lmasdan ilojisi yo‘q.
Distributed System lar bir nechta qismlardan, bir nechta ma’lumotlar bazasidan tashkil topgan bo‘ladi va ushbu qismlar bir biri bilan network orqali gaplashishadi. Bunday holatda esa har doim ham hamma narsa siz kutgandek ishlayvermaydi. Qandaydir muammolar bo‘lib turishi aniq, ayniqsa network bilan. Biror serverda internet sekin ishlashi mumkin, qandaydir DNS muammo bo‘lishi mumkin, packet loss bo‘lishi mumkin va hokazo. Xullas bunday muammo bo‘lishi aniq, 100%.
Shunday holatlarga sizning tizimingiz tayyor bo‘lishi kerak. Oldindan shunday network muammo bo‘lsa nima qilamiz deb o‘ylab qo‘yish kerak.
Bunda bizga CAP nazariyasi yordam beradi. Unga ko‘ra sistemalarda uch xil xususiyat bor:
- [C] Consistency - Ma’lumotlar bazasidan sistemaning barcha qismlari nimadir o‘qimoqchi bo‘lganida eskirib qolgan ma’lumotni olmaydi, eng oxirgi yozilgan ma’lumotlarni oladilar.
- [A] Availability - Tizim har doim ishlab turadi.
- [P] Partition tolerance - Network bilan muammo bo‘lganda ham tizim kutilgandek ishlaydi.
Tepada aytib o‘tdikki network bilan muammolar har doim bo‘ladi va ushbu nazariyaga ko‘ra siz faqatgina yoki Consistency ni yoki Availability ni tanlashga majbursiz. Ikkalasini birdaniga tanlay olmaysiz. Ya’ni sizda har doim P bo‘ladi, siz C yoki A ni tanlashingiz shart.
Masalan sizda Master database va uning replikasi bor. Foydalanuvchilar Masterga yozadi, ma’lumotlarning nusxalari replikaga boradi va replikadan foydalanadiganlar eng oxirgi (ya’ni consistent) ma’lumotlarni o‘qiy oladilar.
Deylik qandaydir network muammo bo‘ldi va master bilan replika orasida bog‘lanish uzildi.
Endi sizda ikkita yo‘l bor:
Birinchisi - consistency ni prioritetga qo‘yish, ya’ni CP. Master ishlayveradi, replicaga kelayotgan requestlar esa "Database unavailable" degan xatoni oladi.
Ikkinchisi - availability ni prioritetga qo‘yish, yani AP. Master ham replica ham ishlayveradi. Lekin bir biriga yozilgan ma’lumotlarni jo‘natishmaydi. Consistency yo‘qoladi. Foydalanuvchilar eskirib qolgan ma’lumotlarni ko‘rishi mumkin.
Qaysi birini tanlash esa holatga bog‘liq.
Masalan siz Netflix quryapsiz. Agar foydalanuvchilar sal-pal eskirib qolgan ma’lumotlarni ko‘rsa qo‘rqinchli emas Netflix uchun. Shuning uchun ham bu sistemani AP qilish kerak, availability ni prioritetga qo‘yish kerak.
Yana bir misol. Deylik siz biror avialiniyaning sistemasini quryapsiz. Unda parvozlarni qidirish funksiyasi mavjud. Bu holatda ham AP qilgan, ya’ni availabilityni muhib deb topish to‘g‘ri. Chunki foydalanuvchilar sal-pal eskirib qolgan narxlarni ko‘rsa ham unchalik qo‘rqinchli emas. Amma umuman qidira olishmasa - qo‘rqinchli.
Lekin chipta sotib olayotganda esa AC qilish shart. Consistent bo‘lishi kerak. Ma’lumotlar aniq va so‘ngi bo‘lishi kerak. Aks holda bitta o‘rinning chiptasini bir nechta odamga sotib yuborishingiz mumkin. Bu esa - qo‘rqinchli.
@jakhonrakhmonov
Backendni jiddiy o‘rganaman degan dasturchi albatta Distributed System lar haqida o‘rganishi kerak. Chunki minglab, millionlab foydalanuvchilar ishlatadigan sistemalar distributed bo‘lmasdan ilojisi yo‘q.
Distributed System lar bir nechta qismlardan, bir nechta ma’lumotlar bazasidan tashkil topgan bo‘ladi va ushbu qismlar bir biri bilan network orqali gaplashishadi. Bunday holatda esa har doim ham hamma narsa siz kutgandek ishlayvermaydi. Qandaydir muammolar bo‘lib turishi aniq, ayniqsa network bilan. Biror serverda internet sekin ishlashi mumkin, qandaydir DNS muammo bo‘lishi mumkin, packet loss bo‘lishi mumkin va hokazo. Xullas bunday muammo bo‘lishi aniq, 100%.
Shunday holatlarga sizning tizimingiz tayyor bo‘lishi kerak. Oldindan shunday network muammo bo‘lsa nima qilamiz deb o‘ylab qo‘yish kerak.
Bunda bizga CAP nazariyasi yordam beradi. Unga ko‘ra sistemalarda uch xil xususiyat bor:
- [C] Consistency - Ma’lumotlar bazasidan sistemaning barcha qismlari nimadir o‘qimoqchi bo‘lganida eskirib qolgan ma’lumotni olmaydi, eng oxirgi yozilgan ma’lumotlarni oladilar.
- [A] Availability - Tizim har doim ishlab turadi.
- [P] Partition tolerance - Network bilan muammo bo‘lganda ham tizim kutilgandek ishlaydi.
Tepada aytib o‘tdikki network bilan muammolar har doim bo‘ladi va ushbu nazariyaga ko‘ra siz faqatgina yoki Consistency ni yoki Availability ni tanlashga majbursiz. Ikkalasini birdaniga tanlay olmaysiz. Ya’ni sizda har doim P bo‘ladi, siz C yoki A ni tanlashingiz shart.
Masalan sizda Master database va uning replikasi bor. Foydalanuvchilar Masterga yozadi, ma’lumotlarning nusxalari replikaga boradi va replikadan foydalanadiganlar eng oxirgi (ya’ni consistent) ma’lumotlarni o‘qiy oladilar.
Deylik qandaydir network muammo bo‘ldi va master bilan replika orasida bog‘lanish uzildi.
Endi sizda ikkita yo‘l bor:
Birinchisi - consistency ni prioritetga qo‘yish, ya’ni CP. Master ishlayveradi, replicaga kelayotgan requestlar esa "Database unavailable" degan xatoni oladi.
Ikkinchisi - availability ni prioritetga qo‘yish, yani AP. Master ham replica ham ishlayveradi. Lekin bir biriga yozilgan ma’lumotlarni jo‘natishmaydi. Consistency yo‘qoladi. Foydalanuvchilar eskirib qolgan ma’lumotlarni ko‘rishi mumkin.
Qaysi birini tanlash esa holatga bog‘liq.
Masalan siz Netflix quryapsiz. Agar foydalanuvchilar sal-pal eskirib qolgan ma’lumotlarni ko‘rsa qo‘rqinchli emas Netflix uchun. Shuning uchun ham bu sistemani AP qilish kerak, availability ni prioritetga qo‘yish kerak.
Yana bir misol. Deylik siz biror avialiniyaning sistemasini quryapsiz. Unda parvozlarni qidirish funksiyasi mavjud. Bu holatda ham AP qilgan, ya’ni availabilityni muhib deb topish to‘g‘ri. Chunki foydalanuvchilar sal-pal eskirib qolgan narxlarni ko‘rsa ham unchalik qo‘rqinchli emas. Amma umuman qidira olishmasa - qo‘rqinchli.
Lekin chipta sotib olayotganda esa AC qilish shart. Consistent bo‘lishi kerak. Ma’lumotlar aniq va so‘ngi bo‘lishi kerak. Aks holda bitta o‘rinning chiptasini bir nechta odamga sotib yuborishingiz mumkin. Bu esa - qo‘rqinchli.
@jakhonrakhmonov