Why write ADRs?
Over on the GitHub blog, there’s a post by Eli Perkins called Why Write ADRs. ADRs provide documentation for Architecture changes, and I think they are enormously useful.
At Khan Academy, we’ve been using ADRs since the middle of 2017. Our implementation of ADRs combines the document with DACI, a decision making framework. DACI defines the roles Driver, Approver, Contributors, Informed, and helps ensure that decisions can be made by recognizing the people in those roles.
In-memory, instance-based caching
groupcache and Olric are intended to be used like Redis, but the difference is that you don’t run servers on separate instances for them. This can speed up access tremendously.