Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

72%
+6 −1
Q&A Which abstraction should I choose for background services and why?

Which concept is best for managed background services? 1. RunAsync(CancellationToken): interface IWorker { Task RunAsync(CancellationToken cancellationToken = default); } ... IWorker worker =...

1 answer  ·  posted 3y ago by Kir_Antipov‭  ·  last activity 3y ago by Alexei‭

#4: Post edited by user avatar Moshi‭ · 2020-09-12T19:54:12Z (over 3 years ago)
Which concept is best for managed background services?

### 1. `RunAsync(CancellationToken)`:

```csharp
interface IWorker
{
    Task RunAsync(CancellationToken cancellationToken = default);
}

...

IWorker worker = ...;
var source = new CancellationTokenSource();
_ = worker.RunAsync(source.Token);

// And when it's time to shutdown the worker:
source.Cancel();
```

vs

### 2. `RunAsync` and `StopAsync`

```csharp
interface IWorker
{
    Task RunAsync();
    Task StopAsync();
}

...

IWorker worker = ...;
_ = worker.RunAsync();

// And when it's time to shutdown the worker:
await worker.StopAsync();
```
#3: Post edited by user avatar Kir_Antipov‭ · 2020-09-12T19:47:22Z (over 3 years ago)
  • Which concept is best for managed background services?
  • 1. `RunAsync(CancellationToken)`:
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync(CancellationToken cancellationToken = default);
  • }
  • ...
  • IWorker worker = ...;
  • var source = new CancellationTokenSource();
  • _ = worker.RunAsync(source.Token);
  • // And when it's time to shutdown the worker:
  • source.Cancel();
  • ```
  • vs
  • 2. `RunAsync` and `StopAsync`
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync();
  • Task StopAsync();
  • }
  • ...
  • IWorker worker = ...;
  • _ = worker.RunAsync();
  • // And when it's time to shutdown the worker:
  • await worker.StopAsync();
  • ```
  • Which concept is best for managed background services?
  • ### 1. `RunAsync(CancellationToken)`:
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync(CancellationToken cancellationToken = default);
  • }
  • ...
  • IWorker worker = ...;
  • var source = new CancellationTokenSource();
  • _ = worker.RunAsync(source.Token);
  • // And when it's time to shutdown the worker:
  • source.Cancel();
  • ```
  • vs
  • ### 2. `RunAsync` and `StopAsync`
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync();
  • Task StopAsync();
  • }
  • ...
  • IWorker worker = ...;
  • _ = worker.RunAsync();
  • // And when it's time to shutdown the worker:
  • await worker.StopAsync();
  • ```
#2: Post edited by user avatar Kir_Antipov‭ · 2020-09-12T19:47:02Z (over 3 years ago)
  • Which concept is best for managed background services?
  • 1) `RunAsync(CancellationToken)`:
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync(CancellationToken cancellationToken = default);
  • }
  • ...
  • IWorker worker = ...;
  • var source = new CancellationTokenSource();
  • _ = worker.RunAsync(source.Token);
  • // And when it's time to shutdown the worker:
  • source.Cancel();
  • ```
  • vs
  • 2) `RunAsync` and `StopAsync`
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync();
  • Task StopAsync();
  • }
  • ...
  • IWorker worker = ...;
  • _ = worker.RunAsync();
  • // And when it's time to shutdown the worker:
  • await worker.StopAsync();
  • ```
  • Which concept is best for managed background services?
  • 1. `RunAsync(CancellationToken)`:
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync(CancellationToken cancellationToken = default);
  • }
  • ...
  • IWorker worker = ...;
  • var source = new CancellationTokenSource();
  • _ = worker.RunAsync(source.Token);
  • // And when it's time to shutdown the worker:
  • source.Cancel();
  • ```
  • vs
  • 2. `RunAsync` and `StopAsync`
  • ```csharp
  • interface IWorker
  • {
  • Task RunAsync();
  • Task StopAsync();
  • }
  • ...
  • IWorker worker = ...;
  • _ = worker.RunAsync();
  • // And when it's time to shutdown the worker:
  • await worker.StopAsync();
  • ```
#1: Initial revision by user avatar Kir_Antipov‭ · 2020-09-12T19:46:03Z (over 3 years ago)
Which abstraction should I choose for background services and why?
Which concept is best for managed background services?

1) `RunAsync(CancellationToken)`:

```csharp
interface IWorker
{
    Task RunAsync(CancellationToken cancellationToken = default);
}

...

IWorker worker = ...;
var source = new CancellationTokenSource();
_ = worker.RunAsync(source.Token);

// And when it's time to shutdown the worker:
source.Cancel();
```

vs

2) `RunAsync` and `StopAsync`

```csharp
interface IWorker
{
    Task RunAsync();
    Task StopAsync();
}

...

IWorker worker = ...;
_ = worker.RunAsync();

// And when it's time to shutdown the worker:
await worker.StopAsync();
```