Selfhosted

39435 readers

3 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Scale to other countries (lemmy.dbzer0.com)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

Hello everyone !
I have a node app and a PostgreSQL DB in VPS using Docker, with Coolify as a CI/CD, nothing too fancy, you might say.

My question is the following.
I have a lot of read/write on my DB and even the lowest increase in DB latency can have an impact on my users' experience. As my VPS is in France, what could be the best/easiest (selfhosted?) option to solve this problem in other regions (North America, Asia...) ?

Thks in advance 🎄🎁

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 10 months ago (1 children)

Your app and DB should be deployed together in the same datacenter to minimize latency between app and DB. Nothing should be hitting your DB besides your app and any etl tools if applicable. So latency to your DB shouldn't be an issue.

If you need to add redundancy with a deployment in another region you should consider having separate environments between regions with totally separate data which allows you to better manage data protection/export regulations appropriately.

If that doesn't work you'll need a multi region database, a vendor with support for that such as aws rds would be the sanest method but you can always hack it yourself.

There's other options but those require an architecture designed to be heavily distributed and that depends a lot on the nature of your application and you'd ideally hire an architect experienced in such deployments.

[–] [email protected] 1 points 10 months ago

My app and DB are on the same server, even more the same Docker Network. Environments separated by region seem to be the best solution for my use case. I hadn't thought of that at all, thank you very much.