If we are designing a product listing page then CDN will fit for product related details including images videos and reviews but product pricing and stock availability should be excluded in such cases.
All the images, css,JavaScript and html of the page will be cached by CDN. Primarily the use case is a classic fit for CDN since there are global users who would to browse the page within ms rather than seconds. Lastly CDNs would not cache payment pages and specific user content such as personal user data due to regulations.
Hey Deeksha! A distributed database and a content delivery network (CDN) are two different things. A distributed database is a database that is spread across multiple computers or nodes in a network, allowing for data to be stored and processed in a distributed manner. Distributed databases are often used to improve performance, availability, and scalability of data storage and processing. A content delivery network (CDN), on the other hand, is a system of distributed servers that delivers web content (such as images, videos, and static files) to users based on their geographic location, network proximity, and other factors. CDNs are designed to reduce the latency and improve the delivery speed of web content, especially for users located far away from the origin server. While both distributed databases and CDNs involve distributing data across multiple nodes, their purposes and architectures are fundamentally different. A distributed database is primarily used for storing and processing data, while a CDN is primarily used for delivering web content.
Can you explain what is Dynamic Content Delivery I have question regarding CDN. CDN associated with only static content right? Like a HTML File, Audio Files, Video Files Etc where user can access these file from their nearest location Can CDN be also be applicable for dynamic content? For example Status of Air Craft being watched from India when it is flying in USA and assume that the data center in USA As per my understanding, for dynamic content there is no concept of CDN right? In this example the data should come from the DB server from USA . Basically wherever you watch in the world , the status of the flight across the world it has to come from USA .
Thanks for the amazing video I have one question : Although we have stored our static content in CDN server, the backend call to fetch the data (REST APIs) would still go to the origin server right? So how does it benefit us in that case?
Thanks for the question! While CDNs primarily cache and serve static content like images, stylesheets, and scripts, the backend calls to fetch dynamic data (via REST APIs) do typically still go to the origin server. The main benefit of CDNs in this context is reducing the load and latency for serving static resources, which allows the origin server to focus on handling dynamic requests. This improves the overall performance and scalability of your application, as static content is offloaded, freeing up resources on the origin server for faster API response times.
Make sure you're interview-ready with Exponent's system design interview prep course: www.tryexponent.com/courses/s...
If we are designing a product listing page then CDN will fit for product related details including images videos and reviews but product pricing and stock availability should be excluded in such cases.
Really nice comparison between push and pull CDNs, like ours, with a good explanation on advantages in and disadvantages. Thanks
All the images, css,JavaScript and html of the page will be cached by CDN. Primarily the use case is a classic fit for CDN since there are global users who would to browse the page within ms rather than seconds. Lastly CDNs would not cache payment pages and specific user content such as personal user data due to regulations.
What is the answer of the last question is it between the load balancer and product listing service
Is it right ? - After the product listing service and parallel to the DB.
Is distributed DB considered CDN?
Hey Deeksha!
A distributed database and a content delivery network (CDN) are two different things.
A distributed database is a database that is spread across multiple computers or nodes in a network, allowing for data to be stored and processed in a distributed manner. Distributed databases are often used to improve performance, availability, and scalability of data storage and processing.
A content delivery network (CDN), on the other hand, is a system of distributed servers that delivers web content (such as images, videos, and static files) to users based on their geographic location, network proximity, and other factors. CDNs are designed to reduce the latency and improve the delivery speed of web content, especially for users located far away from the origin server.
While both distributed databases and CDNs involve distributing data across multiple nodes, their purposes and architectures are fundamentally different. A distributed database is primarily used for storing and processing data, while a CDN is primarily used for delivering web content.
Can you explain what is Dynamic Content Delivery
I have question regarding CDN.
CDN associated with only static content right? Like a HTML File, Audio Files, Video Files Etc where user can access these file from their nearest location
Can CDN be also be applicable for dynamic content? For example Status of Air Craft being watched from India when it is flying in USA and assume that the data center in USA
As per my understanding, for dynamic content there is no concept of CDN right? In this example the data should come from the DB server from USA . Basically wherever you watch in the world , the status of the flight across the world it has to come from USA .
Thanks for the amazing video
I have one question : Although we have stored our static content in CDN server, the backend call to fetch the data (REST APIs) would still go to the origin server right? So how does it benefit us in that case?
Thanks for the question!
While CDNs primarily cache and serve static content like images, stylesheets, and scripts, the backend calls to fetch dynamic data (via REST APIs) do typically still go to the origin server. The main benefit of CDNs in this context is reducing the load and latency for serving static resources, which allows the origin server to focus on handling dynamic requests. This improves the overall performance and scalability of your application, as static content is offloaded, freeing up resources on the origin server for faster API response times.
Thanks a lot
Wow
We want more such videos ❤❤❤❤
Heard you loud and clear, Raj!
awesome!!
Nice stuff