Async and await are notorious for being contagious. Must all interfaces be Task-based, just in case?

Authored by Mark Seemann, a software architect and consultant, this blog focuses on software design, object-oriented programming, and functional programming principles. Readers can explore articles and discussions on topics such as dependency injection, domain-driven design, and test-driven development. Additionally, they can learn about architectural patterns, design patterns, and best practices for building robust, maintainable software systems.

ploeh blog

Asynchronous (async) and Await are 'contagious,' making it challenging to choose whether interfaces should be Task-based. The discussion revolves around two types of interfaces: those enabling variability/extensibility in behavior, and those supporting automated testing. It outlines strategies for implementing async interfaces when needed and warns against preemptively making interfaces async, as it complicates APIs unnecessarily. It also emphasizes the use of Adapters to bridge synchronous and asynchronous operations.

Should interfaces be asynchronous?