Add synchronous methods back to API

[erick-thompson]

I really like the design and layout of version 3 of the SDK. However, the removal of all synchronous methods is playing havoc with my ability to use it on non-greenfield projects. While I understand that async methods are preferred, can we have the option to use the synchronous methods?

[sstevenkang]

Hi Erick. Is the feature request specifically for .Net Core framework? The version 3 SDK for .Net 4.5 framework support both async and sync. methods--for the most part. Is there a specific service that you would like to see support both sync and async?

[erick-thompson]

Hey Steven,

Yes, I am talking about .net core. Right now I have a number of .net core projects that build .net core and .net 4.6.2, so I need to use the functionality that is common to both. In terms of specific services, dynamo and SQS are the two big ones for me.

Thanks!

[normj]

The reason the .NET Core version only has async is because the underlying http client available in .NET Core only supports async operations. We debated about keeping the sync methods in the .NET Core version and have them just call the async versions and then block. The problem with that is the SDK would not be following best practice for the platform and more importantly it could mask a potential performance problem.

[erick-thompson]

I understand. I have some applications that involve very long pipelines (LINQ/lambdas/maps/etc) that, if they aren't synchronous, involve me having to write a new TaskScheduler, as the async behavior results in more tasks than the default scheduler can deal with. Thanks for the quick response.

[normj]

Closing but appreciate the feedback.