ScyllaDB for high write and read but low insert

i plan to use scylladb for multiplayer game data or for matchmaking that needs to be updated every second

basically i want to use scylladb as a fast in-memory for high-update scenario, i looked into ScyllaDB because it is table-based unlike redis,etcd,memcached

i will have fields that could be updated every second

or should i stick with redis,etcd,memcached?

ScyllaDB can easily support a million writes per second on modern hardware and large nodes. The choice should be based on data size. If you have a few hundred gigabytes or more, and high traffic, then using ScyllaDB makes sense.