this post was submitted on 10 Oct 2023
9 points (64.5% liked)

Programming

17362 readers
337 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
9
Why are (relational) databases preferred over keeping the data in memory? (feddit.de)
submitted 1 year ago* (last edited 1 year ago) by kenspeckle@feddit.de to c/programming@programming.dev
11 comments fedilink hide all child comments
 

Why do so many programs use relation databases instead of loading the data during startup and keeping it in memory? Especially for smaller datasets I would think, that a database adds unnecessary complexity and overhead. Also, a lot of data can be saved using modern RAM and when using an in-memory approach, optimized data structures can be utilised to further improve the performance

Edit: yes I meant relational databases

you are viewing a single comment's thread
view the rest of the comments
[โ€“] fsniper@kbin.social 6 points 1 year ago (1 children)

First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

Second, RDBM systems provide a well defined memory/storage structure and API - "structured query language". This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

Third, It's always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.

[โ€“] thoughts3rased@sopuli.xyz 1 points 1 year ago

And also it may save you down the road.

Sure, your dataset might not be big now but what about in a year's time? It's easier to start out using a database than to have to transition it later.