Database Design of Statistic Tool for a Widgets App

Question

Hi everyone,

We are working on a tool that will let developers create widgets and distribute to some publishers in our network. Publishers will be inserting these widgets to their websites. We want developers and publishers to see how many times (from which areas and some other statistical data) these widgets are displayed or interacted.

Currently we have Developer, Widget, Publisher tables but since we are expecting a 1M+ widget display per day, we cannot put whole interactions on one table. Do you have any suggestion for designing such database?

Thanks in advance.

Answer 1

A hit rate of 1M per day is acceptable for MySQL, for example. If you do the math this means around 12 queries per second, which is by far enough even on modest hardware.

However, if you are designing with scalability in mind you should take a look at Cassandra, MongoDB, etc.

You can google for use-cases for both.