Postgres instance vs image
Hello team π
I am evaluating Railway for our team's infrastructure provider and have a quick question.
Up to now, I was able to create Postgres instances fine. But now, whenever I try to create a new one, it is created as a service (from a Docker image).
Am I missing something? How can I create simple instances?
Thank you for your help.
8 Replies
Project ID:
N/ASolution
Plugins are deprecated, now DB's are served in services
Nothing changes afaik
But now it supports metrics and regions
Also, DB Plugins had a fixed version and you depended on the team updating it, now you can use any version you want from the Docker img
I see. Thanks for the quick reply.
But, can I use Docker containers as a production database?
Yeah, they're meant for production.
Its an acceptable practice, don't worry about it.
But if you really care about production ready dbs u should consider a db focused service, like neon or something else
I'd also like to mention, the now deprecated plugins where also just a docker image under the hood, nothing special actually
the postgres plugin was fixed to version 14, and as of right now the postgres services uses postgres 16
In Railway, out of the box:
You get the DB.
In a specialized DB Service like Neon or Planetscale:
You get the DB.
You get Backups
You get Useful insights and analytics with your Dbs in mind
You get some extra technology to make your db and queries faster
Oh, didn't know this. π
Thanks for helping all π