go-api-boilerplate: github.com/vardius/go-api-boilerplate/cmd/auth/internal/domain Index | Files | Directories

package domain

import "github.com/vardius/go-api-boilerplate/cmd/auth/internal/domain"

Package domain is the heart layer of the software, and this is where the interesting stuff happens. The objects in this layer contain the data and the logic to manipulate that data, that is specific to the Domain itself and it’s independent of the business processes that trigger that logic, they are independent and completely unaware of the Application Layer. There is one package per aggregate and to each aggregate belongs entities, value objects, domain events, a repository interface and sometimes factories. The core of the business logic, such as determining whether a handling event should be registered. The structure and naming of aggregates, classes and methods in the domain layer should follow the ubiquitous language, and you should be able to explain to a domain expert how this part of the software works by drawing a few simple diagrams and using the actual class and method names of the source code.


Package Files

doc.go event_metadata.go

type EventMetadata Uses

type EventMetadata struct {
    Identity  *identity.Identity `json:"identity,omitempty"`
    IPAddress net.IP             `json:"ip_address,omitempty"`
    UserAgent string             `json:"http_user_agent,omitempty"`
    Referer   string             `json:"http_referer,omitempty"`

func (*EventMetadata) IsEmpty Uses

func (m *EventMetadata) IsEmpty() bool


clientPackage client holds client domain logic
tokenPackage token holds token domain logic

Package domain imports 2 packages (graph). Updated 2020-11-24. Refresh now. Tools for package owners.