Disk vs. Memory in Database Storage

Just a guy who loves to write code and watch anime.
Search for a command to run...

Just a guy who loves to write code and watch anime.
No comments yet. Be the first to comment.
Qualities that make outstanding builders.

Bipedal vs quadrupedal: how many legs This is about the number of legs the creature walks on. Bipedal. Two legs. Humans, ostriches, T-rex, kangaroos, most fantasy humanoids. Quadrupedal. Four legs. Do

Intro You hear "lerp" and "smoothstep" everywhere in game dev. They sound like math jargon. They're not. Both are small tools that do the same job: smoothly move from one value to another. The problem

What is Kinematics Kinematics is the math field. It's the study of how things move without worrying about forces (which would be dynamics). FK and IK are the two branches: forward kinematics and inver

Intro Textures are usually the biggest cost in a 3D scene. Memory, bandwidth, and load time all get eaten by them. Resizing them is the obvious lever. There's more. This post is about the less obvious

Databases store data on servers, which can be any computer, including yours. The reliability of data storage, especially in events like power outages, leads to two key concepts: disk and memory storage.
Disk storage writes data to a physical disk, ensuring it remains after a power outage. However, this method is slow for both reading and writing data.
Memory storage uses the computer's RAM for quick data access. It's quick but unstable. Data disappears when power is lost.
Databases balance speed and reliability by using both types of storage. Critical data goes to disk for safety, while frequently accessed data stays in memory for speed.
Understanding disk and memory storage is crucial for database management, balancing data safety with access speed.