Hello, currently researching into Ory Cloud adoption, and my main concern now is the latency of session and permissions checks. A brief search on this Slack tells me that you guys are working on edge caching to mitigate any of such issues, is this ready/close to ready?

Hello @brief-student-90305 AFAIK this is still in development. But we should be able to do something on a per project basis. What are your requirements on latency and where are your users based? fyi @fast-lunch-54279

Hey, yes, we are working on it, we hope to have it released soon for ory sessions 🙂

@magnificent-energy-493 We are trialling Ory Cloud for identities and permissions. Our API manager is performing a

whoami

check at the point of ingress and, while there is some latency (~500ms), it is acceptable. However, when we add a permission check requests become noticeably slower. We suspect issue is, in part, down to the latency between our infrastructure and Ory Cloud. If you are planning deployment to other locations, we’d love to talk further. Our infrastructure is hosted on Azure in Sydney.

Hey Andrew, we will add a session whoami cache that will reduce that latency significantly. Hopefully that will be enough to resolve your issue. It should be usable this month if everything goes well. We will also add new regions soon, probably beginning next year.

@magnificent-engine-41970 as Vincent says, we have ambitious goals to bring down latency substantially. AWS in Australia to our current infrastructure in Europe will add a lot of latency, and our global rollouts in the coming months and quarters will certainly help!

Fantastic, thank you for the update. It sounds like we can hold off any custom caching for whoami checks. What are your plans for Keto Cloud regional deployments? If this is more than 3 months away we will probably deploy Keto locally for now.