Table of Contents

Introduction Installation Projects Tables Inserts Searches Updates Deletes CLI Production Installation Partial Autoscaling Good Practices Conclusion

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. 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. 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.

  4. Put a limit of the number of rows on every search. This would reduce your RAM usage.

  5. You should place your web application and your database on the same private network for speed sake.
< Previous Next >