DataArc.Observer
2.0.0
Prefix Reserved
dotnet add package DataArc.Observer --version 2.0.0
NuGet\Install-Package DataArc.Observer -Version 2.0.0
<PackageReference Include="DataArc.Observer" Version="2.0.0" />
<PackageVersion Include="DataArc.Observer" Version="2.0.0" />
<PackageReference Include="DataArc.Observer" />
paket add DataArc.Observer --version 2.0.0
#r "nuget: DataArc.Observer, 2.0.0"
#:package DataArc.Observer@2.0.0
#addin nuget:?package=DataArc.Observer&version=2.0.0
#tool nuget:?package=DataArc.Observer&version=2.0.0
DataArc.Observer
In-process event dispatch and execution observation for .NET applications.
DataArc.Observer provides lightweight observer infrastructure for applications that need to publish events and react to them through independently registered handlers.
It can be used directly in application execution flows or alongside other DataArc components.
Supports .NET 6 through .NET 10.
Free to Use
DataArc.Observer is available free of charge.
It may be used in personal, commercial, educational, government, and enterprise .NET applications without purchasing a DataArc commercial license.
dotnet add package DataArc.Observer
Features
DataArc.Observer provides:
- In-process event dispatch
- Dependency-injected observer registration
- Independently registered event handlers
- Application outcome observation
- Application-specific event handling
- Separation of application execution from event reactions
- Lightweight integration with standard .NET dependency injection
Observer Registration
Observers are registered through dependency injection.
services.AddDataArcObserver(observer =>
{
observer.Add<DataRepatriationSuccessObserver>();
observer.Add<DataRepatriationFailureObserver>();
});
Application-specific observers can respond to execution events without coupling the operation itself to individual handlers.
Event Dispatch
Events are dispatched through the observable event handler.
await _observableEventHandler.DispatchAsync(events);
Registered observers receive applicable events and react independently.
This allows application execution to remain separate from concerns such as notifications, auditing, failure handling, or application-specific follow-up behavior.
Application Boundaries
An application operation can publish events without needing direct knowledge of the observers that respond to them.
Observers can independently handle concerns such as:
- Execution notifications
- Success handling
- Failure handling
- Audit-related reactions
- Application notifications
- Application-specific follow-up actions
This keeps the primary application operation focused on its execution path while allowing surrounding concerns to respond independently.
DataArc Integration
DataArc.Observer can be used independently.
It is also used by DataArc orchestration components to provide event dispatch and execution observation without coupling orchestrated operations to individual handlers.
Licensing
DataArc.Observer is not a commercial DataArc product.
No commercial DataArc license, subscription, activation, or runtime entitlement is required to use the package in accordance with its license.
See the included license file for full terms.
Documentation
Documentation, implementation guidance, examples, and public demos are available through the DataArc repositories and at dataarc.dev.
Support
For support and enquiries, contact support@dataarc.dev.
DataArc
Structured .NET tooling for complex application boundaries.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.DependencyInjection (>= 10.0.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.0)
-
net6.0
-
net7.0
-
net8.0
-
net9.0
NuGet packages (1)
Showing the top 1 NuGet packages that depend on DataArc.Observer:
| Package | Downloads |
|---|---|
|
DataArc.OrchestrationFramework
DataArc.OrchestrationFramework provides structured application orchestration and data coordination for .NET. Combines DataArc.Orchestrator, DataArc.Observer, and DataArc.EntityFrameworkCore to provide explicit application orchestration, execution observation, Entity Framework Core integration, and coordinated execution across application and persistence boundaries. |
GitHub repositories
This package is not used by any popular GitHub repositories.