Good Practices - Flaarum Tutorials

1. A database doesn't autoscale. So do not open your database to the internet.
   Instead put a web server in front of the database and plug the webserver to the internet


2. For a write-heavy database like a mailbox; do not have a single table for emails. Splitting into many tables would improve the speed of the insertion.
   This is due to mutexes (avoid race conditions in multithreaded environment) and creation of indexes (indexes speed up searches).


3. Flaarum doesn't come with inbuilt backup to support as many cloud environments as possible. You would need to do is, which is simple.
   I suggest saving your table definitions and then the data in probably csv or json. This enables you to operate on the data very easily.


4. Flaarum does lazy deletion for speed sake. If you need to do a full deletion, please call the function TrimTable


5. Do your data validation on the front end (web app or GUI). This is because databases do not autoscale and is a generally faster approach.