Refactoring n-tier application towards vertical slices/DDD-esque architecture: Double dispatch and cyclic dependencies

This page summarizes the projects mentioned and recommended in the original post on /r/dotnet

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • AdaptiveClient

    Library and pattern for creating a scalable, loosely coupled service layer. Build interdependent services that are granular and testable. Inject a single client that allows the application to access the entire service layer. Provision services across multiple providers and transports with almost zero application infrastructure.

  • On a different but somewhat related note, you may run into a situation where you have services that are dependent on each other. This will give some DI containers fits. Look at AdaptiveClient for an easy way to resolve this.

  • AdaptiveClient.EntityFramework.Zamagon

    Demo application for AdaptiveClient.EntityFrameworkCore

  • This demo will also show how to structure your project dependencies.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts