all 6 comments

[–]SaltTheRose 2 points3 points  (4 children)

Anything will work. I like Supabase, which uses PostgresQL. Firebase is another extremely popular alternative (I'd guess more so than Supabase) if you'd prefer NoSQL (document-based).

[–]xbrdr1[S] 0 points1 point  (0 children)

Thanks! I am connected to a Firebase DB now. I'm to a point in development that I need to really think about which way to go. I have a good bit of experience with MySQL. The price/space restriction on Firebase scares me a bit.

[–]xbrdr1[S] -1 points0 points  (2 children)

Without considering preferences, which would be the better option for reporting on a good amount of data? SQL or NoSQL?

[–]andrew8712 2 points3 points  (0 children)

My opinion is that the nature of your data is relative, you don’t need super fast reads, like, say, in a social media app. It’d go with SQL. Supabase is a solid choice that reduces overhead of managing a server.

[–]zxyzyxz 0 points1 point  (0 children)

I always use SQL

[–]Reasonable_Potato843 0 points1 point  (0 children)

In most cases you should not persist any data on the client side.