Tooglz tables getting hit far too often causing spikes in access patterns on cloud

[Som Shankar Bhattacharyya]

Hi,

So we are using togglz in or spring cloud aws project. Now our services uses DynampDB for its own data access usage as well as to save togglz states.

What we have seen in our codes base is a usage pattern of checking if a toggle is on before say calling a method. Now ,lets imagine a situation where you are receiving a list of books that you need to add to the database.

That add method is called in a loop with that enabled check. This is causing the toggle DB to be hit far too often causing access spikes.

My question is , is there a way to strategise these behaviours ?

Maybe , something like having a time strategy on when to hit the state database ?

Maybe something like when there is a check I could configure that I would hit the database.