Dang  Tu

Dang Tu

1658324303

Phỏng Vấn Thiết Kế Hệ Thống

Một cuộc Phỏng vấn Thiết kế Hệ thống thường kéo dài trong 45–60 phút. Mẫu sau sẽ hướng dẫn bạn cách quản lý khoảng thời gian trên các khía cạnh khác nhau của nó -

✅ 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭 𝐂𝐥𝐚𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 - (3–5 𝐦𝐢𝐧)
Đặt câu hỏi làm rõ để hiểu vấn đề và mong đợi của người phỏng vấn.
𝐚) 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬
👉 Các trường hợp sử dụng tập trung để bảo hiểm (MVP)
👉 Các trường hợp sử dụng sẽ không được bảo hiểm
👉 Ai sẽ sử dụng hệ thống
👉 Tổng số / Người dùng hoạt động hàng ngày
👉 Hệ thống sẽ được sử dụng như thế nào
𝐛) 𝐍𝐨𝐧 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬
👉 Hệ thống được đánh giá cao Có sẵn hoặc nhất quán cao? Định lý CAP?
👉 Hệ thống có yêu cầu độ trễ thấp không?
👉 Hệ thống có cần đáng tin cậy không?

✅ 𝐄𝐬𝐭𝐢𝐦𝐚𝐭𝐢𝐨𝐧𝐬 (3–5 𝐦𝐢𝐧)
👉 Kỳ vọng về độ trễ / Thông lượng
👉 Tỷ lệ đọc / ghi QPS (Truy vấn mỗi giây)
👉 Ước tính
lưu lượng
👉 Ước tính bộ nhớ 👉 Ước tính bộ nhớ

✅ 𝐀𝐏𝐈 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Phác thảo các API khác nhau cho các tình huống bắt buộc

✅ 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐒𝐜𝐡𝐞𝐦𝐚 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Xác định loại cơ sở dữ liệu (SQL hoặc NoSQL)
👉 Thiết kế lược đồ như bảng / cột và mối quan hệ với các bảng khác (SQL)

✅ 𝐒𝐲𝐬𝐭𝐞𝐦'𝐬 𝐃𝐞𝐭𝐚𝐢𝐥𝐞𝐝 𝐃𝐞𝐬𝐢𝐠𝐧 (20–25 𝐦𝐢𝐧)
(a) Vẽ / Giải thích các thành phần cấp cao của hệ thống liên quan đến các thành phần bên dưới (nếu được yêu cầu) -
👉 Máy khách (Di động, Trình duyệt)
👉 DNS
👉 CDN
👉 Cân bằng tải
👉 Web / Máy chủ ứng dụng
👉 Microservices tham gia vào việc hoàn thiện thiết kế
👉 Blob / Lưu trữ đối tượng
👉 Proxy / Reverse Proxy
👉 Cơ sở dữ liệu (SQL hoặc NoSQL)
👉 Cache ở các cấp độ khác nhau (Phía máy khách, CDN, Phía máy chủ, Phía cơ sở dữ liệu, Bộ nhớ đệm cấp ứng dụng)
👉 Hàng đợi nhắn tin cho giao tiếp không đồng bộ

(b) Nhận dạng thuật toán / cấu trúc dữ liệu và cách chia tỷ lệ chúng
© Chia tỷ lệ các thành phần riêng lẻ - Chia tỷ lệ ngang & dọc
(d) Phân vùng cơ sở dữ liệu -
i) Phương pháp
👉 Phân vùng ngang
👉 Phân vùng dọc 👉 Phân vùng
dựa trên thư mục
ii) Tiêu chí
👉 Dựa trên phạm vi Phân vùng
👉 Phân vùng dựa trên băm (Bắn nhất quán)
👉 Round Robin
(e) Sao chép & Dự phòng -
👉 Dự phòng - Máy chủ chính và phụ
👉 Sao chép - Sao chép dữ liệu từ nút / cơ sở dữ liệu được nhân bản
(f) Cơ sở dữ liệu
👉 SQL - Sharding, Index, master-slave, master-master, Denormalization
👉 NoSQL - Key-Value, Document, Wide-Column, Graph
(g) Giao thức và tiêu chuẩn giao tiếp như - IP, TCP, UDP, HTTP / S, RPC, REST, Web Sockets

✅ 𝐑𝐞𝐬𝐨𝐥𝐯𝐞 𝐛𝐨𝐭𝐭𝐥𝐞𝐧𝐞𝐜𝐤𝐬 𝐚𝐧𝐝 𝐟𝐨𝐥𝐥𝐨𝐰-𝐮𝐩 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 (2–3 𝐦𝐢𝐧𝐮𝐭𝐞𝐬)

Liên kết: https://medium.com/faun/system-design-interview-18bd1df073dc

#designsystem #systemdesign 

Phỏng Vấn Thiết Kế Hệ Thống
Thierry  Perret

Thierry Perret

1658313480

Entretien De Conception De Système

Un entretien de conception de système dure généralement de 45 à 60 minutes. Le modèle suivant vous guidera sur la façon de gérer la durée à travers divers aspects de celle-ci -

✅ 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭 𝐂𝐥𝐚𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 — (3–5 𝐦𝐢𝐧 to)
poser des questions à l'interviewer
𝐚) 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 👉 Cas
d'utilisation focalisés pour couvrir (MVP)
👉 Cas d'utilisation qui ne seront pas couverts
👉 qui utilisera le système
👉 Utilisateurs actifs totaux / quotidiens
👉 Comment le système sera utilisé
𝐛) 𝐍𝐨𝐧 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬
👉 Le système est-il très le système Disponible ou très cohérent ? Théorème CAP ?
👉 Le système nécessite-t-il une faible latence ?
👉 Le système doit-il être fiable ?

✅ 𝐄𝐬𝐭𝐢𝐦𝐚𝐭𝐢𝐨𝐧𝐬 (3–5 𝐦𝐢𝐧)
👉 Attentes de latence/débit
👉 Rapport lecture/écriture QPS (Requêtes par seconde)
👉 Estimations de trafic
👉 Estimations de stockage
👉 Estimations de mémoire

✅ 𝐀𝐏𝐈 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Décrivez les différentes API pour les scénarios requis

✅ 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐒𝐜𝐡𝐞𝐦𝐚 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Identifiez le type de base de données (SQL ou NOSQL)
👉 schéma de conception comme des tables / colonnes et des relations avec d'autres tableaux (SQL)

✅ 𝐒𝐲𝐬𝐭𝐞𝐦'𝐬 𝐃𝐞𝐭𝐚𝐢𝐥𝐞𝐝 𝐃𝐞𝐬𝐢𝐠𝐧 (20–25 𝐦𝐢𝐧)
(a) Dessiner / expliquer les composants de haut niveau du système impliquant des composants ci-dessous (si nécessaire) -
👉 Client (mobile, navigateur)
👉 DNS
👉 CDN
👉 Balancers de charge
👉 web / Serveurs d'application
👉 Microservices impliqués dans la réalisation de la conception
👉 Blob / Object Storage
👉 Proxy/Reverse Proxy
👉 Base de données (SQL ou NoSQL)
👉 Cache à différents niveaux (côté client, CDN, côté serveur, côté base de données, mise en cache au niveau de l'application)
👉 Files d'attente de messagerie pour la communication asynchrone

(b) Identification des algorithmes/structures de données et manière de les mettre à l'échelle
© Mise à l'échelle des composants individuels - Mise à l'échelle horizontale et verticale
(d) Partitionnement de la base de données -
i) Méthodes
👉 Partitionnement horizontal
👉 Partitionnement vertical 👉 Partitionnement
basé sur l'annuaire
ii) Critères
👉 Basé sur la plage Partitionnement
👉 Partitionnement basé sur le hachage (hachage cohérent)
👉 Round Robin
(e) Réplication et redondance -
👉 Redondance — Serveur primaire et secondaire
👉 Réplication — Réplication des données du nœud/base de données en miroir
(f) Bases de données
👉 SQL — Partage, index, maître-esclave, maître-maître, Dénormalisation
👉 NoSQL — Clé-Valeur, Document, Colonne Large, Graphique
(g) Protocoles et normes de communication tels que - IP, TCP, UDP, HTTP/S, RPC, REST, Web Sockets

✅ 𝐑𝐞𝐬𝐨𝐥𝐯𝐞 𝐛𝐨𝐭𝐭𝐥𝐞𝐧𝐞𝐜𝐤𝐬 𝐚𝐧𝐝 𝐟𝐨𝐥𝐥𝐨𝐰-𝐮𝐩 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 (2–3 𝐦𝐢𝐧𝐮𝐭𝐞𝐬)

Lien : https://medium.com/faun/system-design-interview-18bd1df073dc

#designsystem #systemdesign 

Entretien De Conception De Système

Интервью по проектированию системы

Интервью по проектированию системы обычно длится 45–60 минут. Следующий шаблон поможет вам управлять продолжительностью времени в различных его аспектах.

✅ 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭 𝐂𝐥𝐚𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 (3–5 вопросов
и уточнение ожиданий интервьюера для понимания проблемы.
𝐚) 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 👉 Основные
варианты использования для покрытия (MVP)
👉 Примеры использования, которые не будут покрыты
👉, кто будет использовать систему
👉 Общая/ежедневные активные пользователи
👉 Как будет использоваться
система 𝐛) 𝐍𝐨𝐧 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬
👉 - это система высокой степени Доступный или высокосогласованный? Теорема CAP?
👉 Требует ли система низкой задержки?
👉 Должна ли система быть надежной?

✅ 𝐄𝐬𝐭𝐢𝐦𝐚𝐭𝐢𝐨𝐧𝐬 (3–5 𝐦𝐢𝐧)
👉 Ожидаемая задержка/пропускная способность
👉 Соотношение QPS (количество запросов в секунду) при чтении/записи
👉 Оценки трафика
👉 Оценки
памяти 👉 Оценки памяти

✅ 𝐀𝐏𝐈 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Определение различных API для необходимых сценариев

✅ 𝐒𝐜𝐡𝐞𝐦𝐚 𝐃𝐞𝐬𝐢𝐠𝐧 𝐃𝐞𝐬𝐢𝐠𝐧 (3–5 𝐦𝐢𝐧)
👉 Определите тип базы данных (SQL или NOSQL)
👉 Схема проектирования, как таблицы/столбцы и отношения с другими таблицами (SQL)

✅ 𝐒𝐲𝐬𝐭𝐞𝐦'𝐬 𝐃𝐞𝐭𝐚𝐢𝐥𝐞𝐝 𝐃𝐞𝐬𝐢𝐠𝐧 (20–25 𝐦𝐢𝐧)
(a) Нарисуйте /объясните высокие компоненты системы, включающую ниже (если необходимо) Компоненты -
👉 Клиент (мобильный, браузер)
👉 DNS
👉 CDN
👉 Балансиры нагрузки
👉 Интернет / Серверы приложений
👉 Микросервисы, участвующие в выполнении проекта
👉 Хранилище BLOB-объектов/объектов
👉 Прокси/обратный прокси
👉 База данных (SQL или NoSQL)
👉 Кэш на различных уровнях (Клиентская сторона, CDN, Серверная сторона, Сторона базы данных, кэширование на уровне приложения)
👉 Очереди сообщений для асинхронной связи

(b) Идентификация алгоритма/структур данных и способа их
масштабирования © Масштабирование отдельных компонентов — Горизонтальное и вертикальное масштабирование
(d) Разбиение базы данных —
i) Методы
👉 Горизонтальное разбиение
👉 Вертикальное разбиение
👉 Разбиение на основе каталогов
ii) Критерии
👉 На основе диапазонов Разбиение на разделы
👉 Разбиение на основе хэшей (согласованное хеширование)
👉 Циклический алгоритм
(e) Репликация и избыточность -
👉 Избыточность — первичный и вторичный сервер
👉 Репликация — репликация данных с активного на зеркальный узел/базу данных
(f) Базы данных
👉 SQL — сегментирование, индексы, мастер-ведомый, мастер-мастер,
денормализация 👉 NoSQL — ключ-значение, документ, широкий столбец, график
(g) Протоколы и стандарты связи, такие как — IP, TCP, UDP, HTTP/S, RPC, REST, веб-сокеты.

✅ 𝐑𝐞𝐬𝐨𝐥𝐯𝐞 𝐚𝐧𝐝 𝐟𝐨𝐥𝐥𝐨𝐰 𝐮𝐩 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 (2–3 𝐦𝐢𝐧𝐮𝐭𝐞𝐬)

Ссылка: https://medium.com/faun/system-design-interview-18bd1df073dc

#designsystem #systemdesign

Интервью по проектированию системы
田辺  亮介

田辺 亮介

1658291684

系統設計面試

系統設計面試通常持續 45-60 分鐘。以下模板將指導您如何管理其各個方面的持續時間 -

✅ 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭 𝐂𝐥𝐚𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 - (3-5 𝐦𝐦𝐢𝐧)

𝐚)𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥👉專注
用例覆蓋(MVP)
👉將無法覆蓋的用例
👉誰將使用該系統
👉總/每日活躍用戶👉如何使用該系統
如何使用
𝐛)
可用還是高度一致?CAP 定理?
👉系統是否需要低延遲?
👉系統需要可靠嗎?

✅ 𝐄𝐬𝐭𝐢𝐦𝐚𝐭𝐢𝐨𝐧𝐬 (3–5 𝐦𝐢𝐧)
👉 延遲/吞吐量期望
👉 QPS(每秒查詢數)讀/寫比率
👉 流量估計
👉 存儲估計
👉 內存估計

✅𝐀𝐏𝐈(3–5𝐦𝐢𝐧)
👉概述了所需方案的不同API

(3-5𝐦𝐢𝐧)👉(3-5𝐦𝐢𝐧)
👉確定數據庫(SQL或NOSQL)的類型(SQL或NOSQL)
👉設計架構(如表),例如表格/列和與其他表的關係(SQL)

(20–25𝐦𝐢𝐧)
(a)繪製 /解釋以下系統的高級組件(如果需要的話)組件 -
👉客戶端(移動,瀏覽器)
👉dns👉dns👉cdn👉加載
balancer應用服務器👉 實現設計所涉及的微服務 👉 Blob / 對象存儲👉 代理/反向代理👉 數據庫(SQL 或 NoSQL)👉 各級緩存(客戶端、CDN、服務器端、數據庫端、應用程序級緩存)👉 消息隊列用於異步通信

(b) 算法/數據結構的識別和擴展它們的方法
© 擴展單個組件 — 水平和垂直擴展
(d) 數據庫分區 -
i) 方法
👉 水平分區
👉 垂直分區
👉 基於目錄的分區
ii) 標準
👉 基於範圍分區
👉基於哈希的分區(一致哈希)
👉循環
(e)複製和冗餘
-👉冗餘-主服務器和輔助服務器
👉複製-從活動到鏡像節點/數據庫的數據複製
(f)數據庫
👉SQL-分片,索引, master-slave, master-master,
Denormalization 👉 NoSQL — Key-Value, Document, Wide-Column, Graph
(g) 通信協議和標準,例如——IP、TCP、UDP、HTTP/S、RPC、REST、Web Sockets

✅𝐑𝐞𝐬𝐨𝐥𝐯𝐞𝐚𝐧𝐝-𝐟𝐨𝐥𝐥𝐨𝐰-𝐮𝐩(2–3𝐦𝐢𝐧𝐮𝐭𝐞𝐬)

鏈接:https ://medium.com/faun/system-design-interview-18bd1df073dc

#designsystem #systemdesign 

系統設計面試
Grace  Edwards

Grace Edwards

1652030100

Data Scientist Interview - Machine Learning Project System Design

This is going to be a different videos from my regular Coding tutorials. Today we are talking about High-Level System design round that most FAANG companies do for Data Scientist or Machine Learning Engineers role. This round would be ideally your second or third round.

#datascientist #machinelearning #systemdesign 

Data Scientist Interview - Machine Learning Project System Design
Amber  Lubowitz

Amber Lubowitz

1646002620

How to build Classes in Object Oriented Design

Learning system design is not a one time task. It requires regular effort and consistent curiosity to build large scale systems. Moreover, every system has different requirements and meeting them requires expertise and people with varied and specific knowledge. There are a lot of resources to learn through videos. But not everyone enjoys that mode of learning. Instead some people understand things better by reading and thinking on the points put forward by the author. Such people can access these in different ways - blogs, articles and books. We have come up with this video to put light on one such aspect, that is - Fundamentals of objects and classes

TIMESTAMPS
00:00 - Intro
00:44 - Essentials
01:06 - Relationship among Classes
04:15 - Responsibilities of Classes
07:59 - Abstraction and Encapsulation
9:58 - Summary
10:20 - Outro

#systemdesign 

How to build Classes in Object Oriented Design
Amber  Lubowitz

Amber Lubowitz

1645988100

How to Design Low Level Applications using Objects and Classes

Learning system design is not a one time task. It requires regular effort and consistent curiosity to build large scale systems. Moreover, every system has different requirements and meeting them requires expertise and people with varied and specific knowledge. There are a lot of resources to learn through videos. But not everyone enjoys that mode of learning. Instead some people understand things better by reading and thinking on the points put forward by the author. Such people can access these in different ways - blogs, articles and books. We have come up with this video to put light on one such aspect, that is - Fundamentals of objects and classes

TIMESTAMPS
00:00 - Intro
01:34 - What are Objects and Classes?
05:21 - What is NVT technique?
08:12 - Summary
08:54 - Outro

#systemdesign 

How to Design Low Level Applications using Objects and Classes
Amber  Lubowitz

Amber Lubowitz

1645980780

Low Level Design (LLD) Simplified in 6 Steps

Learning system design is not a one time task. It requires regular effort and consistent curiosity to build large scale systems. Moreover, every system has different requirements and meeting them requires expertise and people with varied and specific knowledge. There are a lot of resources to learn through videos. But not everyone enjoys that mode of learning. Instead some people understand things better by reading and thinking on the points put forward by the author. Such people can access these in different ways - blogs, articles and books. We have come up with this video to put light on one such aspect, that is - Components of low level system design.

TIMESTAMPS
00:00 - Intro
00:07 - What is LLD?
03:48 - What does this course covers?
04:15 - What is Advanced LLD ?
05:05 - Types of LLD Interviews
06:35 - Summary

#systemdesign 

Low Level Design (LLD) Simplified in 6 Steps
Amber  Lubowitz

Amber Lubowitz

1645973460

Eventual Consistency in Distributed Systems Explained (1 minute)

Eventual Consistency in Distributed Systems Explained (1 minute)

#softwareengineer  #systemdesign 

Eventual Consistency in Distributed Systems Explained (1 minute)
Amber  Lubowitz

Amber Lubowitz

1645958880

Highly Available Systems Explained in 1 Minute

Highly Available Systems Explained in 1 Minute

#softwareengineers  #systemdesign 

Highly Available Systems Explained in 1 Minute
Amber  Lubowitz

Amber Lubowitz

1645951620

Partition Tolerance Explained in 1 Minute

Partition tolerance Explained 1 Minute

#developer #systemdesign 

Partition Tolerance Explained in 1 Minute

Design Three Tier Architecture and Scalable Secure

Design Three Tier Architecture, and make it highly available, scalable, and secure.

#architecture #systemdesign 

Design Three Tier Architecture and Scalable Secure
Cody  Lindgren

Cody Lindgren

1626149940

Proxy Server | Open Proxy | Reverse Proxy

In this video we study about Proxy server, advantages and disadvantages of using proxy servers, and types of proxy server.
Complete System Design playlist: https://www.youtube.com/playlist?list=PL1w8k37X_6L-ixYtstrwVbB3J1aZuvkg1
Leetcode Problems and Solutions playlist: https://www.youtube.com/playlist?list=PL1w8k37X_6L86f3PUUVFoGYXvZiZHde1S
Graphs Data Structures playlist: https://www.youtube.com/playlist?list=PL1w8k37X_6L9IfRTVvL-tKnrZ_F-8HJQt
Deep Learning playlist: https://www.youtube.com/playlist?list=PL1w8k37X_6L95W33vEXSE9jXJOfvNB3l8

#ProxyServer #ReverseProxy #OpenProxy #VPN #SystemDesign

#proxyserver #reverseproxy #systemdesign

Proxy Server | Open Proxy | Reverse Proxy
Lia  Morar

Lia Morar

1625884740

Why You Should Learn System Design?

If you’re preparing for a tech interview, especially for SDE 2 or SDE 3 job profiles - then you probably would’ve known that you’re required to have a sound knowledge of System Design concepts. However, what you all need to know is System Design is not meant for just cracking these tech interviews - but it is something much vast than that. In fact, not only for experienced working professionals but System Design is also worth it to learn for college students or freshers as well.

To thoroughly explain to you the importance of System Design or why you should learn System Design - we have an expert Yogita Sharma with us who is currently working as an SDE II at Careem (Uber). Yogita will provide you with some of the prominent reasons that are good enough to get started with System Design.

Check Out Yogita’s Youtube Channel - sudoCODE [https://www.youtube.com/channel/UCMrRRZxUAXRzjai0SSoFgdw]

Check out our System Design – Live Course[https://practice.geeksforgeeks.org/courses/system-design-live]

00:00 Let’s Start
00:35 Should You Learn System Design as a Fresher?
00:48 Want a Career Transition to Become a Backend Developer?
01:05 Learn System Design as Full Stack/Front-End Developer
02:27 Must for Principal Engineer or Solution Architect
03:15 System Design via Troubleshooting On-Call Production Issues
04:18 Interview Preparation For Senior SDE Positions
04:37 Closing Notes

This video is contributed by Yogita Sharma.
Linkedin Profile - https://www.linkedin.com/in/yogita-sharma-83400b55/

Please Like, Comment, and Share the Video with your friends.

#systemdesign #softwaredeveloper #geeksforgeeks #interviewpreparation #backend #softwareengineer

Install our Android App:
https://play.google.com/store/apps/details?id=free.programming.programming&hl=en

If you wish, translate into the local language and help us reach millions of other geeks:
http://www.youtube.com/timedtext_cs_panel?c=UC0RhatS1pyxInC00YKjjBqQ&tab=2

Follow us on our Social Media Handles -

Twitter- https://twitter.com/geeksforgeeks
LinkedIn- https://www.linkedin.com/company/geeksforgeeks
Facebook- https://www.facebook.com/geeksforgeeks.org
Instagram- https://www.instagram.com/geeks_for_geeks/?hl=en
Reddit- https://www.reddit.com/user/geeksforgeeks
Telegram- https://t.me/s/geeksforgeeks_official

Also, Subscribe if you haven’t already! :)

#developer #systemdesign #softwareengineer #backend #interviewpreparation

Why You Should Learn System Design?

Planning Of integrating form and System Design with AWS | How to Make Facemash

Tryout the demo site (devlopment stage) of College Facemash : http://cfm-react.s3-website-us-east-1.amazonaws.com/

Landing Page of College Facemash: https://collegefacemash.com

The whole journey of making facemash: https://www.youtube.com/playlist?list=PL83X-jRLQqGGTDlCmLLzgnLpMY3xo1Nj8

#AWS #Cognito #SystemDesign

If you have any suggestions, Queries or any though just leave it in comment and I’ll be happy to get back to you

FIND ME HERE:
facebook: https://facebook.com/MeRahulAhire
Instagram: https://instagram.com/merahulahire
Twitter: https://twitter.com/MeRahulAhire
LinkedIn: https://linkedin.com/in/merahulahire

#cognito #systemdesign #aws

Planning Of integrating form and System Design with AWS | How to Make Facemash