You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are you trying to accomplish? Please describe.
I'm trying to understand why most (if not all) queries from this app are annotated with @cacheControl(scope: PRIVATE).
My understanding is that fetched reviews shouldn't vary by user and therefore they can be cached.
When we use PRIVATE as the scope we make all queries to be executed as POST requests, which make them bypass all platform caches.
Triggers false alarms that overload platform on-call engineer.
Opens our ingress circuit breaker, making the cluster as a whole unstable.
I understand that it may not be trivial to debug the leak, but if caching responses is an option it may reduce the app load to the point where the leak is not relevant and instabilities do not hamper the whole platform.
What are you trying to accomplish? Please describe.
I'm trying to understand why most (if not all) queries from this app are annotated with
@cacheControl(scope: PRIVATE)
.My understanding is that fetched reviews shouldn't vary by user and therefore they can be cached.
When we use
PRIVATE
as the scope we make all queries to be executed asPOST
requests, which make them bypass all platform caches.Since there is no cache, reviews and ratings account for 15~20% of our ingress requests. To make matters worse, the app has a leak which makes it overuse resources and become unstable. And when the app fails, our border error rate increases, which:
I understand that it may not be trivial to debug the leak, but if caching responses is an option it may reduce the app load to the point where the leak is not relevant and instabilities do not hamper the whole platform.
Additional info
ReviewsByProductId
,AppSettings
,AverageRatingByProductId
,TotalReviewsByProductId
are all private queries executed asPOST
requests.The text was updated successfully, but these errors were encountered: