@Aaronontheweb@OlympicDrankz Local calls with Orleans don’t go through the network and you can also opt out of the deep copy isolation of messages if you want to live dangerously and need all the perf. Or was there something else you meant by local only?
@p_mbanugo@davidfowl We use YARP as a gateway in to multiple k8s clusters (packaged multi-cloud, multi-cluster ingress/gateway solutions don’t really exist) and it works great. Also happen to use Orleans there for the few services that need session affinity.
@danpdc@mjovanovictech Dynamic config is great, too, if you need it. We have a multi-cluster k8s ingress where multiple clusters write their config (routes/backends) to object storage then YARP pulls all of those, merges them, and updates its routes. Built off the InMemory provider with a timer added.
@jbogard Links vs parent is really a use case specific decision. Some use cases want to tell different stories than others through the data. That sequence diagram is really slick though.
@eulerfx@reubenbond What kind of functionality are you looking for in that? Listing active grains or grains with persistent state? Filtering on those like secondary indexes or map/reduce?
@CFDevelop YARP as our reverse proxy and the made an Orleans based rate limiter implementation to do distributed rate limiting across all instances. Could also do the same rate limiting implementation in the service if using another load balancer.