Invstigate: the pros / cons of moving the hit counts into a database

[jxmot]

Currently, each individual use of the hit counter creates a simple text file that contains a number.

PROs:

• Fast, the code is minimal and executes quickly

CONs:

• No other information is retained when hit occurs, such as the date/time of the count.
• Unable to determine any sort of trending on when hit counts are occuring.

---

Database Candidates:

The choice for a database will follow these criteria:

• Must be hosted locally: I use a hosting service that currently provides MySQL. I've been working on setting up MongoDB to run on the same server(s).
• A minimum of overhead code.
• Easy to set up, and use for others. Since a "cloud" hosted database isn't going to be used there isn't any requirement to create any additional accounts for a database service.
• Must have a small footprint. The intent here is to allow small platforms like Raspberry Pi, Beagle Board, etc, to be used as a hosting server for the counters.

So far there are two possible candidates:

MySQL

• Pros:
  • Readily avilable on most hosting servers, in some cases MariaDB is in place of MySQL and works nearly identically.
• Cons:
  • Some set up is required for the necessary table(s).

MongoDB Community

Not readily available on most hosting servers.

SleekDB

Found at https://github.com/rakibtg/SleekDB. Seems active.

Looks like a decent flat DB solution for PHP. But may be over complicated for use here.

---

[jxmot]

Closing this issue for now.

Implemented simple JSON formatted count log files.