in this system we only needs to map the video with its view
hence there is only 2 columns that needs to be kept together
Choices
SQL database
database such as mysql can be used to deal this type of problem by storing video_id, and view count in table Views
video_id will act as primary key while views_count will behave like one of the usual column
noSQL database
in this use case we can also apply noSQL database, to be more specific key-value database.
We only need to keep video_id as key and views_count as value.
So key-value database such as dynamodb from AWS is more suitable for this problem
Decision
In this case, the design would benefit from using key-value database.
While the structure of data is consistent across the system's life sql database is known for its complexity for scaling. Action like sharding is far more complex than its noSQL database
And as there is only 2 columns we can safely use key-value database.