# AlphaYu/adnc

A pragmatic .NET 8 framework for modular monoliths to evolve seamlessly into distributed microservices.

Repository: https://github.com/AlphaYu/adnc
Canonical: https://ross.abutalabs.com/products/adnc
Homepage: https://aspdotnetcore.net
Language: C#
License: MIT
License Family: permissive
Topics: microservices, ddd, dapr, aspnet-core, clean-architecture, distributed-systems, dotnet, dotnet8, event-bus, infrastructure, modular-monolith
Last push: 2026-04-29T17:32:56+00:00

## Health v2 (maintenance only)
Score: 73/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 79, release rhythm 49, longevity 100
- inputs: {"age_days": 2222, "days_push": 126, "days_rel": 129, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1476, forks 392 (observed 2026-08-28T04:04:50.264270+00:00)

## What it is
ADNC is an open-source .NET 8 framework for building modular business systems that can start as modular monoliths and evolve into distributed microservices. It bundles reusable infrastructure packages, an Ocelot API gateway, shared service layers, demo DDD-style services, and Docker Compose deployment assets.

## Use cases
- build a modular monolith in .NET that can later split into microservices
- set up an API gateway with routing and authentication for .NET services
- implement DDD-style services with clean architecture in ASP.NET Core
- add event-driven integration between services with CAP and RabbitMQ
- bootstrap production infrastructure like Consul, Redis, and centralized config for .NET
- learn microservice architecture patterns through a working reference implementation

## When to choose
- you are on .NET 8 and want strict module boundaries from day one
- you want a pragmatic path from monolith to microservices without premature complexity
- you need batteries-included infrastructure: gateway, discovery, config, auth, events, caching, observability
- you want a reference implementation showing multiple service shapes coexisting

## When to avoid
- you need a lightweight minimal API scaffold without distributed-systems machinery
- your team does not use .NET/C#
- you want a fully managed platform rather than a self-hosted framework
- you prefer assembling your own stack from individual libraries

## Facets
- artifact type: framework
- maturity: active
- function: web-framework, api-framework, api-gateway, middleware, auth, caching, message-queue, service-discovery, microservices, configuration-management, tracing, orm
- domain: microservices, backend, web-development, developer-tools, apis
- platform: dotnet, cross-platform, windows
- tags: ddd, modular-monolith, clean-architecture, ocelot, consul, dapr, event-driven-architecture, reference-implementation, dotnet8, rabbitmq, redis, docker, web-server, linux, macos

## Member repositories
- AlphaYu/adnc (main) score 73

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:50.264270+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:34:25.971323+00:00, confidence not recorded.
  - readme: https://github.com/AlphaYu/adnc (fetched 2026-08-28T04:04:50.264270+00:00, sha 92582ecf02c9)
  - homepage: https://aspdotnetcore.net (fetched 2026-08-29T11:41:37.035301+00:00, sha e2491cf09f90)
  - site_page: https://docs.aspdotnetcore.net (fetched 2026-08-29T11:41:37.044324+00:00, sha ea26a0f70e7c)
- Data as of 2026-08-30T08:39:29.467469+00:00.