Database Development

Designing an (almost) Read only database

I want to create a database with 3 main entities each of which will be subtyped further(by subtype I mean generalization-specialization).

This database will support a website where the users can ONLY Read the database. I don’t know how many users will hit the website daily.
As I see vision it, the database will have a TOTAL of 500,000 rows.

Once a week I would like to update the database with around 10 records in ALL in various entities.

Should I use InndoDB? What optimizations can I make since this will be a “mostly read” database. Is it sensible to stop the website for 5 minutes and upload the weekly 10 records? Or can that be done online?

Leave a Reply

Your email address will not be published. Required fields are marked *