Closed samvaity closed 3 weeks ago
@srnagar Let us know if plan to switch DPG/Cadl to sync stack. (<-- OK, Cadl probably later, there is some complicities in the case of convenienceAPI call protocolAPI)
Sync stack could have some downside for client customization. Previously they can customize in async client, and add one line in sync client to call e.g. client.doLro().getSyncPoller()
. <-- currently I guess only loadtesting did this kind of customization, so likely not having big impact if we switch by default
Done for all SDKs.
Sync stack - Partner team onboarding
Steps to onboard sync stack workflow for SDK's:
Add
enable-sync-stack: true
toCode generation settings
in respective swagger/autorest.md Using this generation setting, autorest should generate sync equivalent overloads for all the API's.Enable AssertingClient Testing, this makes sure sync call API's are running in completely synchronous call stack.
Validate the changes by running the LIVE test pipeline on the PR.
Run Perf analysis and compare data to understand the impact of the changes.
DPG SDK's to be onboarded: