Homelab

22 readers

1 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

a single database for several services in proxmox? [DISCUTION] (alien.top)

submitted 11 months ago by roycorderov@alien.top to c/homelab@selfhosted.forum

2 comments fedilink hide all child comments

what's up folks,
I am always looking for how to improve my infrastructure and these days I have been thinking about the feasibility of creating an lxc container or a vm in my proxmox just to install a db like mariadb and all the other services in another lxc's that will need a db for example wordpress, odoo, speedtest tracker, n8n etc. will point to that lxc or vm with the db of mariadb (or another)...

would it be good?, would it be bad? Would it be a good practice? Would it provide any bad performance? or would it be a benefit?

what do you think?

top 2 comments

sorted by: hot top controversial new old

[–] mss-cyclist@alien.top 1 points 11 months ago

I prefer one database server instance hosting different databases, for each client service one.

[–] NC1HM@alien.top 1 points 11 months ago

It's really hard to tell, and the devil is in the details.

On bare metal, a single server containing both the front-end application and the DB may be faster (no networking overhead), but only to a point. As load increases, a split system (front-end on one machine, DB on another, or even on a cluster) becomes more attractive.

When everything is virtualized and machines talk to each other over virtual interfaces, I would think a single database server usable by multiple front-end applications would be a good idea. This way, you have only one DB server overhead. Also, maintenance is more straightforward; you look after a single database server, even though it contains multiple databases.

It's probably a good idea to pair each application with a dedicated database (within the same database server) and assign each application a unique user name with rights only for that database.