A customer can give hints about what to optimize for, relatively simple configuration i.e. single broad switch #5488
Labels
bulk-closed
Priority:2
Work that is important, but not critical for the release
Team:Runtime
User Story
A single user-facing feature. Can be grouped under an epic.
.NET offers both high-level and low-level configuration knobs, but nothing in-between or that describes intent. In the cloud world, people are typically either concerned about controlling cost or maximizing performance. We aspire for .NET defaults (#5485) to be some mid-point between the two, with a bias to maximizing performance.
We should consider configuration knobs that enables developers, or deployment/cloud admins, to configure applications in terms of intent. It's possible we will enable setting multiple intents, ordered in terms of priority. The following is a first approximation of what those "intents" might be, with a mix of orientation on resources and outcomes:
More research needs to be done here. At present, this ideas (while seemingly attractive) are bordering on theory.
The text was updated successfully, but these errors were encountered: