Proactive Resilience Engineering

The article might talking about using cache policy (memory cache) to handle duplicated requests (might comes from same identity: IP address or…) and acting with expected controlling.

Image that we have main service API that serve user authentication affairs. And we got one block list according the specific IP address that we would like to control and logs if any request belong to the list. The usual code flow might looks as below:

So far the code section works without any logical problem. But suppose If the same identity request coming in the instance highly frequency (maybe every 2–3 seconds per request). The logs function will consume the server resource for log down the meaningless information of duplicated records. we would like to avoid the case which apply cache policy would be the good ideal:

After we apply cache policy that we have expected logs behavior:

Just the simplest example to demonstrate the basic way of proactive resilience programming. So far we have to connect more and more micro service(s) and cloud-based system(s) to serve diverse client(s) nowadays, how to design and stable each system’s component(s) would be important.

Related posts:

Representative stating that he/she of a New York term life insurance policy. In his Platinum Advantage matters and help you policy records. In the mind? New York Life Care Benefit provided the…

Often I find myself having a superficial conversation. When this happens. When I have a conversation filled with light-hearted chatter. A conversation that’s looks exactly like many of the previous…

I am part of the Facebook Generation. In my midteens, I packed my cringe-inducing photos and left Bebo for the bright lights and shiny newness of Facebook. This also means that by my mid-twenties the…