Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Introduction to system scalability and reliability" | Hashnode

Feed/

Discussion

Ahmed Sadman Muhib

Software Engineer @ Optimizely

Jun 19, 2021

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. When you'...

blog.muhib.me12 min read

#cloud #scalability #devops #system-architecture #web-development

Responses2

Markdown supported · ⌘↵ to post

Rafat Islam

Software Engineering

Jul 16, 2021

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

Software Engineer @ Optimizely

Jul 16, 2021

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

Vibing

Jun 19, 2021

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

Software Engineer @ Optimizely

Jun 19, 2021

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.