RDBMS & NoSQL Database Scaling

Vertical Scaling (Scale Up)


  • Since there is only a single node of database, it is easy to implement.
  • The bigger is the server, the faster it gets. (performance-wise)


  • It gets more expensive as your data largen.
  • Difficult to perform parallel operations.
  • Creates some risky situations when database server fails.

Horizontal Scaling


  • It is always the cheaper option compared to vertical scaling.
  • Has a better fault tolerance. Therefore the downtime would be significantly lower.
  • Easy to perform parallel tasks.


  • More difficult to implement. Keeping the consistency between nodes is hard.
  • Not always ideal for RDBMS since the relations between data is difficult when the data is scattered over DB nodes.

Scaling SQL Database Systems

Vertical Partitioning

Horizontal Partitioning (Sharding)

Scaling NoSQL Database Systems




Software Engineer

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Application Containerization using Docker — Oversimplified

Minimal cuDNN C++ Hello World Example

Thou shalt have no unbreakable programming principle

Larix Monthly Review [Dec]

NFT as Service(NaaS) is the Future

Quick tip — how to upgrade to URP in Unity

🤑Two and one Airdrop $XBN💰

Exceptional Application Performance Requires Dev Insight and Ops Weigh-In

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
İsmail GÖK

İsmail GÖK

Software Engineer

More from Medium

How to integrate AWX with WSO2 API Manager?

Blind Index Pattern — Search Strategy for Encrypted Information

Load balancer — [Notes]

CVE-2022–22963 : In Spring Cloud Function versions 3.1.6,