this post was submitted on 11 Jan 2026
292 points (97.4% liked)

Selfhosted

55098 readers
614 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] possiblylinux127@lemmy.zip 21 points 2 weeks ago (2 children)
[–] call_me_xale@lemmy.zip 33 points 2 weeks ago (1 children)

Hell, even SQLite is good enough for most small projects.

[–] dan@upvote.au 23 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

SQLite is underrated. I've used it for high traffic systems with no issues. If your system has a large number of readers and a small number of writers, it performs very well. It's not as good for high-concurrency write-heavy use cases, but that's not common (most apps read far more than they write).

My use case was a DB that was created during the build process, then read on every page load.

[–] derpgon@programming.dev 1 points 2 weeks ago (1 children)

Wow, I never thought about storing build data in an SQLite file. That's quite clever.

[–] dan@upvote.au 9 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

One of SQLite's recommended use cases is as an alternate to proprietary binary formats: https://sqlite.org/appfileformat.html. Programs often store data in binary files for performance, but you get a lot of the same functionality included with SQLite (fast random access, concurrent usage, atomicity, updates that don't need to rewrite the whole file, etc) without having to implement a file format yourself.

I'm not sure if this is still the case, but Facebook'a HHVM used to store the compiled bytecode for the whole site in a single SQLite database: https://docs.hhvm.com/docs/hhvm/advanced-usage/repo-authoritative/. Every pageload loaded the bytecode for all required files from the DB.

[–] 0x0@lemmy.zip 2 points 2 weeks ago

They also have a (one-time fee) encryption extension.

[–] hoppolito@mander.xyz 1 points 2 weeks ago

Fascinating read, I should definitely also make way more use of sqlite for little side projects.
Thanks for the link!

[–] immobile7801@piefed.social 10 points 2 weeks ago (2 children)

FWIW mariadb was bought by a private equity firm in 2024

[–] psoul@lemmy.world 4 points 2 weeks ago

Oh no… it was the easy solution for Wordpress and other plug and play self hosted services .

[–] alibloke@feddit.uk 2 points 2 weeks ago

The corporation was bought by k1 capital. The foundation and therefore the open source version will always be free