Where is the best place to store a frequently changed field? in the general table of goods or separately?

Question

Database design

There are a lot of fields in the product table. These fields are usually changed by the operator and not so often.
Now we need to add the "number of views" field, which will change each time the product is viewed.
Should I add this field directly to the product table, or is it better to create a related table with a
one-to-one relationship? and to change in that table? Which would be better from a design point of view?

Answer 1

I would store it in the cache and drop it into the database only when updating. Well, choose the cache yourself, either you just have a structure, or a radish, or something else

Answer 2

IMHO the number of views has nothing to do with the essence of the product.
It's more of a monitoring thing.
So it makes sense in general to take this logic out of the database.
To some key-value store.

Answer 3

Separate the essence of the product, from the essence of "browsing history" is the best. In essence, "browsing history" in addition to the product index store the date of viewing. Almost 100% managers will want to keep track of all sorts of bursts of views and other analytics. To begin with, you can shove everything into one table, as you grow, you will have to separate the archive logs (for example, for a year) from the operational ones.