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
I agree, we should define either a plugin-wide config parameter that controls the auto partition route behavior (like, generate all partition routes or only the first one) or could be a specific label that controls it per service.
I think it's okay to leave it as is for stateful services, i.e., generate a route for each partition. However, for stateless, I'd be inclined to turn it off globally and provide a label to turn it on as required. I won't get a chance this week but will try get something together over the following week.
I'd like to make the auto-generation of services based on partitions optional (or potenially disable it altogether) for Stateless services.
@dariopb
According to the Microsoft documentation:
"partitioning a stateless service is a very rare scenario--scalability and availability are normally achieved by adding more instances."
At the moment, I'm creating services with custom routers and the auto-generated routers are noisy in my configuration and something I will never use.
I'm happy to create a PR, however, @dariopb, as you're the owner, I'd like to discuss it with you first.
The text was updated successfully, but these errors were encountered: