Access Control Caching Proxy
The main problem of caching http proxy is an invalidation of cache. Nginx invalidates cache by deleting it when expire it's TTL or by HTTP PURGE method in requests or by manual deleting cache. In some case this approach is not enouth. It is not necessary delete cache, more effective update cache by some conditions. For example periodical refreshing cache or by count requests.
- introspection of access tokens and embedding their content to the request body;
- limitig the number of requests to the backend;
- caching of responses;
- periodical refreshing cache or by count requests;
- sending events to queue for business analitics.
Multiple clients asynchronous send identical requests to ACCP, it's reorganizes them in sequenced requests. ACCP passes to back service only first request and all next requests wait answer from first request.