-
Notifications
You must be signed in to change notification settings - Fork 494
DRAFT: Stream API vs Typed responses
j82w edited this page Sep 27, 2019
·
3 revisions
TLDR: Stream APIs for performance. Typed APIs for simple and clean .NET development experience.
- Does not throw service exceptions. Instead returns it as part of the response. This avoids the c# overhead of throwing and catching the exceptions. Argument exceptions are still thrown such as passing a null on a required parameter.
- Stream APIs do not serialize the responses. This allows middle tiered applications to avoid the overhead of deserializing and then re-serializing the response.
- Converts the stream to a c# object which makes it easy to program against.
- Follows the .NET guideline and throws exceptions
- No need to dispose or wrap responses in using statements. All of the disposed types are handled by the SDK.