---
title: "Discussion on \"Database at scale - Introduction\" | Hashnode"
description: "Discussion on \"Database at scale - Introduction\". What is database at scale and how do we approach it in different databases types."
url: "https://hashnode.com/posts/database-at-scale-introduction/66154a28543404353cba4ace"
---

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

Discussion

# [Database at scale - Introduction](https://blog.binyamin.dev/database-at-scale-introduction?utm_source=hashnode&utm_medium=feed)

What is database at scale and how do we approach it in different databases types.

Apr 9, 2024 · 5 min read · blog.binyamin.dev  
Read the article

-   [#databases](https://hashnode.com/tag/databases)
-   [#high-availability](https://hashnode.com/tag/high-availability)
-   [#sharding](https://hashnode.com/tag/sharding)

## Written by

[Binyamin Yawitz](https://hashnode.com/@byawitz)

@byawitz

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

## Responses

Markdown supported · ⌘↵ to post

[Itay Braun](https://hashnode.com/@itayb)

[Apr 12, 2024](https://hashnode.com/posts/database-at-scale-introduction/66154a28543404353cba4ace/comment/661998ed75e737d9a7dc1123)

In recent years, there has been a push in the tech community to move away from using terms like "master" and "slave" due to their association with oppressive and discriminatory contexts. In the context of database architecture, you can replace "master" and "slave" terminologies with more neutral and descriptive terms such as: Primary - Secondary, or Primary - Replica.