Type to search pages and rules.

Browse pages

Overview

The backend pages state how a LiteSpec server application is built: its layers, business model, coordination of use cases, storage, HTTP boundary, testing, and record identifiers, with the .NET binding that realizes each one. A use case is one command or query with its permissions, results, and cases, and a stack is the technology binding a project selected for its backend. A server project applies these pages through its stack, while a product without a server applies only the architecture, domain, application, and identifier pages, so every reader finds the rules for the parts their product has and no others.

Markdown

How the pages fit together#

The seven principle pages directly in this folder hold for every backend. They say what each layer owns and which direction references point, without naming a framework or a package. The .NET Stack states how the .NET backend realizes those principles: its projects, its C# shapes, its Marten persistence, and its test suites. A team that adds a use case reads the principle page for the layer it touches, then the matching .NET page for the binding.

Backend principles#

  • Backend Architecture: the five layers, the direction references point, and the modules and use cases that organize every layer.
  • Domain Layer: aggregates, lifecycles, closed value sets, and repositories, and what Domain never references.
  • Application Layer: use-case coordination, pipeline stages, ports, and event reactions.
  • Persistence: repositories, the read session, the one commit per command, and the obligations on stored data.
  • HTTP API: endpoints, routes, errors, collection paging, and the generated OpenAPI contract.
  • Backend Testing: the test suites each project size keeps and what each suite may use.
  • Record Identifiers: the identifier form for each record type and how citations resolve.

Backend stack#

  • .NET Stack: the .NET binding of every principle page, and the test-result formats the model builder reads.
  • .NET extensions overview: the extensions only a .NET backend offers: executable BDD scenarios and EF Core persistence.