---
title: "Discussion on \"Introduction to system scalability and reliability\" | Hashnode"
description: "Discussion on \"Introduction to system scalability and reliability\". Scalability and reliability are measures of how well your application can be served to end-users. If you have a system that can serve millions of users without noticeable downtime, then we can say the system is highly scalable and reliable.\nWhen you'..."
url: "https://hashnode.com/posts/introduction-to-system-scalability-and-reliability/60ce071e37952431a17126d6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Introduction to system scalability and reliability](https://blog.muhib.me/introduction-to-system-scalability-and-reliability?utm_source=hashnode&utm_medium=feed)

Scalability and reliability are measures of how well your application can be served to end-users. If you have a system that can serve millions of users without noticeable downtime, then we can say the system is highly scalable and reliable. When you'...

Jun 19, 2021 · 12 min read · blog.muhib.me  
Updated Aug 11, 2022  
Read the article

-   [#cloud](https://hashnode.com/tag/cloud)
-   [#scalability](https://hashnode.com/tag/scalability)
-   [#devops](https://hashnode.com/tag/devops)
-   [#system-architecture](https://hashnode.com/tag/system-architecture)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Ahmed Sadman Muhib](https://hashnode.com/@ahmedsadman)

@ahmedsadman

  
[View profile](https://hashnode.com/@ahmedsadman)

Software Engineer @ Optimizely

Software Engineer | Mentor | Cats | Food | Loves to learn

## Responses 2

Markdown supported · ⌘↵ to post

[Rafat Islam](https://hashnode.com/@Rafat)

[Jul 16, 2021](https://hashnode.com/posts/introduction-to-system-scalability-and-reliability/60ce071e37952431a17126d6/comment/60f0e5ea19e3e845d50d05a7)

The problem with master slave architecture is consistency issues due to replication lag. What will happen when the master goes down without syncing some data to the slaves? For that we might need to incorporate other strategy too like synchronous replication, but then again it'll add to the latency. Good read anyway. Please keep writing. Thank you. 😊

[Ahmed Sadman Muhib](https://hashnode.com/@ahmedsadman)

[Jul 16, 2021](https://hashnode.com/posts/introduction-to-system-scalability-and-reliability/60ce071e37952431a17126d6/comment/60f0e5ea19e3e845d50d05a7#reply-60f123a8303c5845ab8ca814)

No and No. Such operations are done asynchronously, whenever master receives write request it will pass them immediately to the replicas. Different solutions have different strategies to sync out of date data. For example, ElasticSearch uses Primary Term and Sequence Number in internal state to handle such issues.

[Monzur Rahman Naafiz](https://hashnode.com/@KarikariNafiz)

[Jun 19, 2021](https://hashnode.com/posts/introduction-to-system-scalability-and-reliability/60ce071e37952431a17126d6/comment/60ce120637952431a17127ec)

Amazing Read! I had an inquiry that if I use a CDN over the site, does that improve the internals of my server/performance anyway, or is it just a location-wise distributed network?

[Ahmed Sadman Muhib](https://hashnode.com/@ahmedsadman)

[Jun 19, 2021](https://hashnode.com/posts/introduction-to-system-scalability-and-reliability/60ce071e37952431a17126d6/comment/60ce120637952431a17127ec#reply-60ce138bc6377540dd23856f)

Both. From location perspective, it will cache, store and optimize _assets_ (video, images, html etc) to your nearest server so that it's served to you as fast as possible. From server perspective, it reduces the actual load on the server because the assets are already cached and stored in other places, thus no need to hit the servers.
