tbwork / anole Goto Github PK

Background

One friend recently asked me that how Anole tackles with the situation that if one worker is shutdown unexpectedly and some clients could receive the latest value in real-time and the others not (those clients would retrieve the latest value in several seconds after re-connect with the new worker ). And my answer at that time is :

In terms of my experience in Ctrip and DaZhongDianPing(DZDP), their real-time configuration framework (Apollo in Ctrip and Lion in DZDP) allows delayed configuration update. By the way, the situation of unexpected shutdown of one work server is very unusual and the client still could retrieve
old values from the local cache.

However, there is indeed some situations that the clients should retrieve the latest configurations in real-time, it requires immediate re-connect with new worker and get the new value rather than the delayed detection of connection-broken by the LCM(long connection manager).

Solution

So, my plan is to provide a new feature named "volatile", it can be specified in the **getProperty(...)" like:

Anole.getProperty(key, volatile); 

The parameter of volatile is a bool value, true means retrieving data from the server first every time.

Sometimes we want to update certain configuration at certain specified time like 12:00 at midnight.
Anole would provide such a mechanism to support this.