shriek-fx
A .NET Core rapid development framework implementing DDD and CQRS patterns for event-driven, event-sourced applications.
What is shriek-fx?
ShriekFx is a rapid development framework for .NET Core that implements Domain-Driven Design (DDD) and CQRS patterns. It provides infrastructure for building event-driven, event-sourced applications with features like command/event buses, event storage, and eventual consistency. The framework simplifies the adoption of complex architectural patterns by offering out-of-the-box components and extensible modules.
Developers and teams building .NET Core applications who want to implement DDD, CQRS, and event-driven architectures without building infrastructure from scratch. It's particularly suited for small to medium-sized applications transitioning to microservices.
ShriekFx offers a constrained, opinionated framework that makes DDD and CQRS accessible, reducing the learning curve and implementation overhead. Its extensible design, support for multiple storage backends, and contract-as-a-service feature provide flexibility while enforcing best practices.
Overview
An easy-to-use rapid development framework developed on the basis of.NET Core 2.0, following the constraints of domain Driven Design (DDD) specifications, combined with the CQRS architecture to provide the infrastructure for event-driven, event backtracking, responsiveness, and more. Let developers enjoy the true meaning of object-oriented design patterns brought by the aesthetic.
Use Cases
Best For
- Implementing Domain-Driven Design in .NET Core applications
- Building event-sourced systems with multiple storage options (e.g., EF Core, Redis, InfluxDB)
- Developing microservices with CQRS and eventual consistency
- Rapid prototyping of business systems using DDD patterns
- Creating scalable architectures with event-driven communication
- Automating client-server code generation via contract-as-a-service
Not Ideal For
- Applications targeting .NET 5 or later, as it's built on the outdated .NET Core 2.0
- Projects needing out-of-the-box UI components or GraphQL support, as these features are marked incomplete
- Teams requiring immediate, strong consistency models, since it enforces eventual consistency
- Enterprises needing stable, fully-documented production frameworks, given its pre-release status and limited English docs
Pros & Cons
Pros
The framework enforces DDD principles with built-in components like command and event buses, reducing implementation overhead and guiding developers towards best practices.
Supports multiple backends such as EF Core, Redis, InfluxDB, and LiteDB for event sourcing, allowing teams to choose based on performance and scalability needs.
Generates client and server code from defined interfaces for HTTP and Socket protocols, cutting down on boilerplate and accelerating API development.
Follows Ports and Adapters, enabling integration with third-party libraries like RabbitMQ and SmartSql, and scaling from monoliths to microservices.
Cons
Built on .NET Core 2.0, which is no longer supported by Microsoft, limiting access to newer .NET features and security updates.
Many advertised components like Actor patterns, Saga, GraphQL, and UI layers are marked as [ ] in the task list, indicating they are not production-ready.
Requires adding a MyGet feed for installation and has dependencies on multiple external libraries, increasing initial configuration effort.
Only Chinese documentation is explicitly mentioned, posing a barrier for non-Chinese speaking developers and reducing accessibility.
Frequently Asked Questions
Related Projects
MediatRSimple, unambitious mediator implementation in .NET
MassTransitDistributed Application Framework for .NET
Marten.NET Transactional Document DB and Event Store on PostgreSQL
EventFlowAsync/await first CQRS+ES and DDD framework for .NET
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.