Projects with synchronous and asynchronous Apis

Question

I am developing a small project and have, for now, two entities:

• Product and Customer

Product API is asynchronous (with Task and async) and client API is synchronous.

I would like to know if there is a problem in using these two approaches in the same project? What are the problems, if any?

Another question is also when it is actually recommended to use asynchronous Apis in projects?

Answer 1

In principle no problem. Of course, the moment they intertwine the synchronous will always prevail and the synchronous stop will cause waiting at that point, but if you are inside something being called asynchronously that part will still maintain competition. If you synchronously call a code in an asynchronous method this call will be synchronous, and only one call to this calling method will be asynchronous, which may not be relevant.

Remember that async is useful for IO, so the last case I mentioned should not have an advantage under normal conditions. The IO operation has to be originally asynchronous to have gains. If the execution is too fast it doesn’t pay to use such a heavy mechanism. It establishes a minimum of 50ms of running time (not cake recipe), which is relatively rare to have such operations. Only with large volumes or some very slow IO will give gain.

In processing, competition or even parallelism with thread and not with async.

I answered in more detail in other questions:

• When using asynchronous or synchronous method?
• It’s always guaranteed that a multi-threaded application runs faster than using a single thread?
• What are Async Methods?
• In C#, what is the await keyword for?
• There are differences between the terms Thread, Multithread, Async and Await?
• What is the difference between async, multithereading, parallelism and competition?
• The keyword "async" actually makes the asynchronous method?
• Difference between Task and Thread