I'm going to build a tool to automate social media posts, so i will need to save a lot of data regarding the posts of each user for each social they have connected to their account. Besides that i will need to have on my server a code that will call my database each minute and check if it should post something at that time ( since they are scheduled per request of the user )
To me this doesn't sound like highly relational data. I think a nosql document database would be fine. But the main question is where do you host or do you have a service provider? Because then the best is to use something your provider already has.
If AWS I would say use Dynamo DB.
If Google then I'd use firebase's document database.
If something like heroku, I'd use their mongoDB plugin.etc
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm going to build a tool to automate social media posts, so i will need to save a lot of data regarding the posts of each user for each social they have connected to their account. Besides that i will need to have on my server a code that will call my database each minute and check if it should post something at that time ( since they are scheduled per request of the user )
A standard relational database will handle this perfectly fine. Postgres is versatile and will handle the use case.
To me this doesn't sound like highly relational data. I think a nosql document database would be fine. But the main question is where do you host or do you have a service provider? Because then the best is to use something your provider already has.
If AWS I would say use Dynamo DB.
If Google then I'd use firebase's document database.
If something like heroku, I'd use their mongoDB plugin.etc