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 stack binding that realizes each one. A use case is one command or query with its access, results, and scenarios; a reaction answers an event without a request, and a job runs work on a schedule or by hand. 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 layers their product has and no others.

Markdown

How the Pages Fit Together#

The eight 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 shared kernel and modules projects with their hosts, its C# shapes, and its Marten persistence. 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 four layers, the direction references point, and the module tree that organizes every layer.
  • Domain Layer: aggregates, lifecycles, closed value sets, and domain repositories, and the boundary that keeps technical concerns out of business rules.
  • Application Layer: use-case coordination, pipeline stages, ports, reactions, jobs, and declared effects.
  • Persistence: domain 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.
  • Write Code for a Use Case: where each code element of a use case goes, the mark it carries, and the check that watches it.

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.