aspdotnetcore.net

What It Is

ADNC is an open-source .NET 8 framework positioned for business system development with a “modular monolith first, evolvable to microservices” approach. It is not just a collection of framework packages; it also provides a gateway, demo services, database scripts, and deployment assets, emphasizing a runnable reference implementation to help teams put architectural conventions into practice.

Core Capabilities

Based on the main description, ADNC covers common enterprise backend infrastructure: Ocelot gateway, Consul service discovery and configuration center, CAP + RabbitMQ event messaging, Redis caching, distributed locks, Bloom filters, JWT security, HealthChecks, Polly resilience policies, as well as NLog + Loki and SkyAPM + SkyWalking observability. For data access, it supports EF Core and Dapper, and involves MySQL, SQL Server, and MongoDB. It also provides building blocks for shared application layers, domain layers, repository layers, remote calls, and Web APIs.

Architecture and Ecosystem

ADNC’s defining feature is that it first defines service ownership and module boundaries, then extracts microservices only when scale or operational benefits become clear. This path is more pragmatic than adopting full microservices from the start. The sample services include admin management, operations logs, customer, order, and warehouse services, and demonstrate layered, compact, and DDD-style structures, making it useful for teams comparing different ways to organize services.

Pricing and Open Source

The main text explicitly labels ADNC as open-source and provides a GitHub entry point, with no mention of a commercial edition, SaaS hosting, or paid support. The license type, enterprise services, maintenance SLA, and community size are not disclosed, so its support model should be verified further.

Pros, Cons, and Best Fit

Its strengths are a complete infrastructure stack, concrete reference implementations, and tight integration with the .NET 8 ecosystem. It is well suited to medium and large business systems such as enterprise backends, order and warehouse systems, and permission/organization management. The limitations are that the technology stack is relatively heavy and primarily aimed at .NET teams; for smaller projects, it may introduce too many components. The main text also does not clarify release cadence, contribution activity, or long-term support strategy.

Access from China

The main text does not provide information about domestic mirrors, network availability, or payment, so china_access is unknown. If GitHub or the online demo is unstable to access, teams in China may consider setting up their own repository mirror and private deployment. Alternatives worth watching include ABP Framework, Dapr, Orleans, and Spring Cloud Alibaba.