Express YourSelf !

Each pod will have local bucket and then implement leaky bucket algorithm. 

Start bucket size with big number

Learning from rate limiting journey

Service with smaller threshold has higher precision

higher threshold has upto 10% error rate

pod has its own swimlane 

-------------------------------------------------------------------------

For inter+intra rate limit, need to synch API-GW and serviceMesh. 

Unified config management 

Naavik knows, where service resides (Kubecon Paris) 

Canary release pattern : First canary call, the service registry will read from DB and put it in cache. For remaining, no need to access DB. Response from cache. Canary pod can put value in S3 bucket, for further optimization, and notify all pods to read form s3 bucket