I am interested to hear what database tech people are using. I have just gone with what the Agent set up, which is PostgreSQL. I know that likes Supabase. I’m not knowledgeable enough to really know what other options there are and what the pros/cons of different options might be.
I am doing this for fun and I am happily funding it all myself so far and so want to keep costs way way down. But I guess the app does have the potential for wider use and so a robust solution is warranted.
Any thoughts of db I should look at? Or is the Replit PostgreSQL going to do the job OK? I don’t want to overengineer it just for the sake of it.
I stick to PostgreSQL in the Replit environment. I like the DB backups with Neon, which provide point-in-time restoration. Neon’s PITR is great, but you’ll want to adjust the retention period to control storage costs if you’re dealing with an enormous dataset.
Also, Replit’s environment is out-of-the-box more secure, with SOC2. For that level of security with Supabase, for example, it appears you’d have to be on the $599/mo. plan. (what?!)
You could also use Firestore on Firebase, which scales nicely on the paid plan. For my needs thus far, I don’t see a reason to shy away from robust Postgres/Neon config within Replit env.
1 Like
Thanks @realfunnyeric good to hear. Being new I’m still figuring it out. And the people that use the Replit options often don’t post about it as much so it is easy to feel that you need to use other options when you keep hearing about how others are doing it.
Replit has spent a lot of time building a robust platform, bringing an awful lot of value for what we pay (overages excluded, ha). Still not a fan of the auth, so I go elsewhere for that, usually Firebase as I’ve said, because my workflow there is solid and effortless, but others have luck with Supabase and Clerk.
But every application is different, so explore and do what works for you!
3 Likes
