My DB will end up with about 50GBs of data before it goes live and will grow steadily over time. I have a droplet on Digital Ocean via Laravel Forge just to get the proof of concept built. For long term sustainability how would you architect the DB?
Is a droplet sufficient? Better to use a managed SQL instance, load balancers or what? I know some of this will depend on the amount of traffic the site receives, no idea what that may look like at this point.
I have never built an application with this large of a DB.
For one thing archive (backup) older data into another database. It is still available however.
Like:
Learn how to use partitions. Just examples.
Basically learn database management, there is a lot to it besides just queries.
And there are numerous tutorials on load balancing, Digital Ocean has help articles.
@signalwarrant We have no idea because we don’t know what data you’re storing or why.
It's game play statistics that I'll create unique views of. All the data will need to be available to the app. I'm storing the data because the API is prone to go down, didn't want to take a dependency on the external API.
Please or to participate in this conversation.