adnc

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

Why ADNC · Design Principles · Architecture · Getting Started · Documentation

简体中文 · English

What Is ADNC?

ADNC is an open-source .NET 8 framework for building modular business systems that can evolve from modular monoliths into distributed microservices. It brings together the infrastructure, conventions, and sample services that teams typically need when building production-grade systems: gateway routing, service discovery, centralized configuration, authentication, inter-service communication, event-driven integration, persistence, caching, observability, resilience, and deployment support.

The repository is both a framework and a working reference implementation. It includes reusable Adnc.Infra.* packages, shared service-layer packages, an Ocelot gateway, a multi-service demo domain, database scripts, Docker Compose infrastructure assets, and English/Chinese documentation.

ADNC is intentionally not a one-size-fits-all template. It demonstrates how different service shapes can coexist in the same system: classic layered services, compact single-project services, and DDD-style services with explicit domain layers.

Why ADNC

Distributed systems fail most often at the boundaries. Service ownership, data consistency, configuration drift, and integration contracts are where real complexity lies. ADNC focuses on solving these boundary challenges rather than just scaffolding simple controllers and repositories.

ADNC is built on three core pillars:

• Modular Monolith First – Design with strict boundaries from day one. Stop the "Big Ball of Mud" before it starts.
• Strategic Evolution – Extract services only when scale justifies complexity. Distributed systems are a cost, not a feature.
• Enterprise Infrastructure – Production-ready building blocks for .NET 8. Focus on business behavior, not plumbing.

Use ADNC when you need:

• A Strategic Baseline: A pragmatic .NET 8 framework that balances simplicity and scalability.
• Seamless Evolution: A path to evolve modular monoliths into distributed microservices without massive rewrites.
• Architectural Discipline: Consistent infrastructure abstractions (Caching, Messaging, Auth) across services.
• Production Realism: A demo including Gateway, Identity, CAP (Event Bus), SkyWalking (Tracing), and more.

ADNC is not:

• A black-box platform that hides .NET application architecture.
• A code generator that produces architecture without intent.
• A microservice-only template that forces every bounded context to be deployed independently from day one.
• A benchmark claim. Performance notes are scenario references, not guarantees.

Design Principles

Modular first, distributed when necessary Service boundaries should be explicit before deployment boundaries become expensive. ADNC helps teams establish clear modular boundaries first and introduce distributed deployment only when it is actually needed.

Different domains deserve different shapes A simple CRUD service shouldn't be forced into the same complexity as a domain-heavy service. ADNC promotes informed trade-offs across different project styles.

Shared Infrastructure, Owned Business Logic Cross-cutting concerns (Caching, Repositories, Events, Logging) are centralized in reusable building blocks. Business logic remains pure and isolated within service-specific Application and Domain layers.

Operational concerns are first-class citizens Configuration, Tracing, Gateway routing, and HealthChecks are treated as core architectural requirements, not operational afterthoughts.

Prefer replaceable integrations over reinvention ADNC orchestrates the best of the .NET ecosystem—Consul, Cap, EF Core, Dapper, Redis, SkyAPM—behind consistent conventions rather than reinventing the wheel.

Architecture at a Glance

At a high level, ADNC is organized into four parts:

Infrastructure Packages

The src/Infrastructures directory contains reusable packages under the Adnc.Infra.* namespace.

• NuGet: packages matching adnc.infra

Shared Service Packages

The src/ServiceShared directory contains reusable service-level building blocks under the Adnc.Shared.* namespace.

• NuGet: packages matching adnc.shared

Core Capabilities

Technology Stack

Repository Structure

…

Important Solutions

Build configuration is centralized through:

• src/Directory.Build.props: shared build settings, including net8.0, nullable reference types, implicit usings, package metadata, and documentation generation.
• src/Directory.Packages.props: Central Package Management for NuGet versions.
• src/.editorconfig: cross-editor code style configuration.

Getting Started

The fastest way to get started is to follow the quick start guide. The demo requires infrastructure such as Consul, Redis, RabbitMQ, MySQL, logging components, and service configuration, so the startup sequence matters.

1. Install the .NET 8 SDK.
2. Read the ADNC Quick Start Guide.
3. Open src/Adnc.sln for framework packages or src/Demo/Adnc.Demo.sln for demo services.
4. Prepare infrastructure from the quick start guide or the Docker Compose assets in deploy/staging.
5. Initialize demo data from database/mysql/adnc.sql.
6. Start the gateway and demo services in the documented order.

For Docker-oriented setup, use the Quick Docker Deployment Guide.

Demo Domain

The demo contains five business services and shared cross-service contracts. Each service uses a different structure to make the architectural trade-offs visible.

| Service | Business Scope | Architecture Style