Is having multiple databases per instance problematic?
xevion
HOBBYOP

a year ago

railway is the typical default database created; I'm still looking into what options I have, but either it was create a second instance, or use a second database within the same instance. I can't figure that there's anything wrong with this, but everything I know currently about traditional use dictates that you only have 1 database in use, the rest are system databases not typically accessed during normal usage.

Solved

7 Replies

xevion
HOBBYOP

a year ago

5bce27d5-0216-4700-b2fc-f3a7f9644cba


xevion
HOBBYOP

a year ago

My use case is having a OAuth2 Next.js app hosted with a Directus (headless CMS).


xevion
HOBBYOP

a year ago

Prisma, my ORM for Next.js, does not like having tables it doesn't know (such as those created by Directus, by me or it's internal system).


xevion
HOBBYOP

a year ago

*I am about to go to sleep, I just tested this to see if there was any problem, and it's seems to be perfectly fine; but I thought I would ask here. I'll see notifications to any replies in the morning.


xevion
HOBBYOP

a year ago

If you're wondering "what does this guy want to be told"; Yes/No and any detail about your personal experience with multiple databases within the same instance hosted in Docker/Railway. It's a small question.


adam
MODERATOR

a year ago

Having multiple databases is not an issue. From what I've seen, it does not contribute significantly to costs


adam
MODERATOR

a year ago

!s


Status changed to Solved adam about 1 year ago


Loading...