How deeply does Learn Go with Pocket-Sized Projects cover domain layer?

Implements validation, defaults, generated fields, typed errors, persistence orchestration, and focused tests.

Domain layer

As explained in Learn Go with Pocket-Sized Projects

A domain layer is an architectural layer that contains an application's business rules and domain behavior independently of delivery and persistence concerns.

The domain layer, also called the business layer, owns business rules and domain behavior rather than transport-specific concerns. It exposes typed business concepts such as Habit, ID, Name, and WeeklyFrequency, making APIs clearer and reducing accidental argument mix-ups. section 10.3.1

A domain operation can:

Return domain errors without knowing that an API uses gRPC; the API layer translates invalid input into INVALID_ARGUMENT. section 10.3.1

Creating a habit

Create validates and completes a Habit, saves it to data storage, and returns the completed entity. Tests cover fully populated, partially populated, and whitespace-only names.

How Learn Go with Pocket-Sized Projects covers it

Cover of Learn Go with Pocket-Sized Projects

liveBook manning.com

Read Learn Go with Pocket-Sized Projects on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe application layer that contains domain concepts, rules, and business logic independently of external communication and infrastructure responsibilities.
liveBook manning.com

Grokking SimplicityThe architectural layer containing domain rules and calculations while remaining independent of external services.

Compare how 3 books explain domain layer →

Related concepts

hexagonal architecturepart of · Hexagonal architecture is a software architecture pattern that isolates an application’s core logic from external systems through ports and adapters.
service layerused by · A service layer is a distinct software-architecture layer that provides application-level functionality or services through interfaces to other components or applications.
multi-tier applicationpart of · A multi-tier application is an application organized into distinct tiers that separate responsibilities and interact through defined dependencies or interfaces.
interface layerused by · An interface layer is a software architectural layer that mediates interactions between consumers and application functionality or external services through defined interfaces.
idempotency keyproduces · An idempotency key is an identifier associated with a logical operation that lets a service recognize repeated requests and prevent duplicate effects.
infrastructure layercontrasts with · An infrastructure layer is an architectural layer that provides technical capabilities and connects application functionality to resources such as databases, messaging systems, and external services.

This explainer was generated by Manning's knowledge graph from the text of Learn Go with Pocket-Sized Projects. The section links point to the parts of the book it draws on.