Async

Here is a simple explanation of the difference between synchronous and asynchronous API calls.

This is an update to an earlier post on caching Tasks and only executing them when first accessed. This version uses Lazy<Task> to hold the Task.

Here’s a simple example of using a lock in a Web API action method. But you probably shouldn’t.

By default, the Confluent Kafka client consumes one message at time, but with a bit of work it can consume batches of messages.

Caches are usually used to store concrete values, but with C# you can store tasks for work you want to perform only once, at the time the key is first requested from the cache.

I usually want to run a task immediately, but there are times when I want to create a task, but not start it until later. This post will show you how to do defer execution of a task.

The Consume method of the Kafka Confluent library for C# is synchronous, this post shows you how to use it in a non-blocking way.

This post shows you how to use a synchronous call in a background service without blocking the application or other background services.

When sending a cancellation request to a method that returns a value, you must return a value or throw an exception. Here is how to throw the exception.

Here is an example of using a cancellation token to stop the execution of a method.