62 packages returned for Tags:"domain-driven-design"

A base repostitory implementation to be used in message-drive, CQRS-based architectures

Implementation of Domain Driven Design Value Object in .NET

Domain driven design components and marker interfaces.

J3DI is a Domain-Driven Design framework for .NET Core and is intended to be minimalistic & cross-platform. This package, J3DI.Domain, is the foundation and may be used stand-alone.

The BullOak.Repositories implementation for EventStore

J3DI is a Domain-Driven Design framework for .NET Core and is intended to be minimalistic & cross-platform. This package, J3DI.Domain, is the foundation and may be used stand-alone.

J3DI is a Domain-Driven Design framework for .NET Core and is intended to be minimalistic & cross-platform. This package, J3DI.Domain, is the foundation and may be used stand-alone.

The BullOak.Repositories implementation for NEventStore

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Data access abstractions.

Abstractions for domain driven design

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Core package of the framework.

$ dotnet new -i Paulovich.Caju::0.7.3 $ dotnet new manga It generates a .NET Solution following the Clean Architecture Style, DDD and Separation of Concerns in Domain, Application, Infrastructure and UI.

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Base domain model package.

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Framework infrastruture package - event stores, projections, jobs, etc.

The BullOak.Repositories implementation for EntityFramework

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Configurable user notifications extension package.

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Entity Framework Core (EF Core) implementation of infrastructure services.

Base and helper classes/interfaces for domain-driven design

We are a hybrid event source as a service. You can use a fully indexed and powerful event source that is highly scalable and fast as hell. Or you can use document style data storage to simply persist state. Or you can use both, we're cool like that.

Event Sourcing, CQRS and DDD framework for modern C#/.NET applications. Infrastructure for testing framework apps.