Users Created Event

Verified Scenario

This page is generated from an executable spec. An automated suite renders a fresh App from the current GoForj templates, applies every step below in order, and runs every verification command. If any step fails, the page does not ship.

Scenario 4 of 7 in the verified path. Plan on about 25 minutes.

This scenario extends the user profile flow with a POST /api/v1/users endpoint that publishes a typed users.created event after a user is saved.

The event announces that something happened. The subscriber reacts to it. Durable background work, retries, and worker lifecycle belong in a job and queue, which the next scenario introduces.

What You Will Build

EVENTS_* config selects the local event driver.
internal/events.UserCreated defines the typed event.
users.Service publishes through a small application boundary.
notifications.Subscribers delivers users.created through a small handler interface.
app/lifecycle.go registers and closes the subscription.
Focused tests prove service publication, in-process subscriber delivery, and POST route registration.

Prerequisites

Complete File Upload to Storage first.

Your App should have event support enabled. Verify that the generated event package exists:

text

internal/events

Golden Path State

Before this scenario, the App can read cached user profiles and store uploads, but user creation has no application event boundary.

After this scenario, creating a user also publishes a typed users.created fact. A subscriber reacts to the event through lifecycle-registered wiring, but queue-backed work is still left for the next job scenario.

Files

This scenario edits or creates:

Configuration

text

.env

Events

text

internal/events/user_created_event.go

Users feature

text

internal/users/repository.go
internal/users/events.go
internal/users/service.go
internal/users/service_test.go
internal/users/controller.go
internal/users/controller_test.go

Notifications

text

internal/notifications/service.go
internal/notifications/subscribers.go
internal/notifications/subscribers_test.go

Lifecycle and wiring

text

app/lifecycle.go
app/wire/inject_services_app.go

The event generator updates manager files, and the rendered App includes the tested concurrent logger implementation.

text

internal/events/accessors_gen.go
internal/events/manager_gen.go
internal/logger/app.go
internal/logger/dedupe_test.go

Do not edit generated event or logger files by hand.

Step 1: Refresh Event Resources

The generated environment already selects the in-process event driver for local development. Run the build pipeline so your App exposes app.Bus() and app.Events().

bash

forj build

Step 2: Add the Event

Create internal/events/user_created_event.go.

Events should be small typed facts. They should not carry full domain objects, request payloads, or driver-specific metadata.

Create or replace internal/events/user_created_event.go:

// Package events defines application events without exposing driver-specific details.
package events

// UserCreatedTopic keeps publishers and subscribers on one stable routing key.
const UserCreatedTopic = "users.created"

// UserCreated carries only the identity needed by downstream reactions so the event remains portable across drivers.
type UserCreated struct {
	UserID string `json:"user_id"`
	Email  string `json:"email"`
}

// Topic binds UserCreated to its routing key without adding transport metadata to the payload.
func (UserCreated) Topic() string {
	return UserCreatedTopic
}

Step 3: Extend the Repository

Replace internal/users/repository.go.

The repository still owns source-of-truth storage and cache-aside reads. This example uses memory so the scenario stays local and runnable.

Create or replace internal/users/repository.go:

// Package users keeps user behavior independent from HTTP and infrastructure details.
package users

import (
	"context"
	"fmt"
	"strconv"
	"sync"
	"time"

	"github.com/goforj/cache"
)

// profileCacheTTL bounds how long this runnable example can serve a profile without consulting its source of truth.
const profileCacheTTL = 5 * time.Minute

// UserRepository keeps persistence replaceable while the service owns user workflows.
type UserRepository interface {
	// Find keeps source-of-truth reads behind the repository boundary.
	Find(ctx context.Context, id string) (User, error)
	// Save keeps ID assignment and persistence behind the repository boundary.
	Save(ctx context.Context, user User) (User, error)
}

// MemoryUserRepository keeps the scenario runnable without requiring a database service.
type MemoryUserRepository struct {
	mu     sync.RWMutex
	nextID int
	users  map[string]User
}

// NewMemoryUserRepository seeds the profile used by earlier steps while reserving the next ID for creation.
func NewMemoryUserRepository() *MemoryUserRepository {
	return &MemoryUserRepository{
		nextID: 43,
		users: map[string]User{
			"42": {
				ID:    "42",
				Name:  "Ada Lovelace",
				Email: "[email protected]",
			},
		},
	}
}

// Find permits concurrent reads while protecting the map from HTTP writes in the runnable App.
func (r *MemoryUserRepository) Find(_ context.Context, id string) (User, error) {
	r.mu.RLock()
	defer r.mu.RUnlock()

	user, ok := r.users[id]
	if !ok {
		return User{}, ErrUserNotFound
	}
	return user, nil
}

// Save serializes ID assignment with persistence so concurrent requests cannot claim the same ID.
func (r *MemoryUserRepository) Save(_ context.Context, user User) (User, error) {
	r.mu.Lock()
	defer r.mu.Unlock()

	if user.ID == "" {
		user.ID = strconv.Itoa(r.nextID)
		r.nextID++
	}
	r.users[user.ID] = user
	return user, nil
}

// CachedUserRepository adds cache-aside reads without leaking cache concerns into the user service.
type CachedUserRepository struct {
	source       UserRepository
	profileCache *cache.Cache
}

// NewCachedUserRepository requires both the source of truth and cache because neither dependency is optional.
func NewCachedUserRepository(source UserRepository, profileCache *cache.Cache) *CachedUserRepository {
	return &CachedUserRepository{
		source:       source,
		profileCache: profileCache,
	}
}

// Find falls back to the source of truth on a cache miss and repopulates the bounded profile entry.
func (r *CachedUserRepository) Find(ctx context.Context, id string) (User, error) {
	key := profileCacheKey(id)

	user, ok, err := cache.Get[User](r.profileCache.WithContext(ctx), key)
	if err != nil {
		return User{}, fmt.Errorf("read user profile cache: %w", err)
	}
	if ok {
		return user, nil
	}

	user, err = r.source.Find(ctx, id)
	if err != nil {
		return User{}, err
	}

	if err := cache.Set(r.profileCache.WithContext(ctx), key, user, profileCacheTTL); err != nil {
		return User{}, fmt.Errorf("write user profile cache: %w", err)
	}

	return user, nil
}

// Save writes through to the source before refreshing the cache so failed persistence is never cached.
func (r *CachedUserRepository) Save(ctx context.Context, user User) (User, error) {
	user, err := r.source.Save(ctx, user)
	if err != nil {
		return User{}, err
	}
	if err := cache.Set(r.profileCache.WithContext(ctx), profileCacheKey(user.ID), user, profileCacheTTL); err != nil {
		return User{}, fmt.Errorf("write user profile cache: %w", err)
	}
	return user, nil
}

// profileCacheKey namespaces profile entries so user IDs cannot collide with other cache data.
func profileCacheKey(id string) string {
	return "users:" + id + ":profile"
}

Step 4: Add an Event Publisher Boundary

Create internal/users/events.go.

The service will depend on UserEvents, not on global App state. That keeps tests direct and keeps the event boundary visible.

Create or replace internal/users/events.go:

// Package users keeps user behavior independent from HTTP and infrastructure details.
package users

import (
	"context"

	"your/module/internal/events"
)

// UserEvents keeps user workflows independent of App state and generated event drivers.
type UserEvents interface {
	// PublishCreated announces a persisted user only after the source-of-truth write succeeds.
	PublishCreated(ctx context.Context, user User) error
}

// UserEventPublisher translates user workflow results into the application's event contract.
type UserEventPublisher struct {
	bus events.Bus
}

// NewUserEventPublisher requires the application bus because publishing is part of successful user creation.
func NewUserEventPublisher(bus events.Bus) *UserEventPublisher {
	return &UserEventPublisher{bus: bus}
}

// PublishCreated keeps the event payload small so subscribers do not depend on the full User model.
func (p *UserEventPublisher) PublishCreated(ctx context.Context, user User) error {
	return p.bus.WithContext(ctx).Publish(events.UserCreated{
		UserID: user.ID,
		Email:  user.Email,
	})
}

Step 5: Publish from the Service

Replace internal/users/service.go.

The service owns the application workflow: validate, save, publish. The repository owns cache-aside access. The controller still owns HTTP concerns.

Create or replace internal/users/service.go:

// Package users keeps user behavior independent from HTTP and infrastructure details.
package users

import (
	"context"
	"errors"
	"fmt"
	"strings"
)

var (
	// ErrUserNotFound lets transports map a missing user without parsing an error message.
	ErrUserNotFound = errors.New("user not found")
	// ErrNameRequired distinguishes invalid creation input from repository failures.
	ErrNameRequired = errors.New("name is required")
	// ErrEmailRequired distinguishes invalid creation input from repository failures.
	ErrEmailRequired = errors.New("email is required")
)

// User is the stable application representation shared by service and transport boundaries.
type User struct {
	ID    string `json:"id"`
	Name  string `json:"name"`
	Email string `json:"email"`
}

// CreateUserInput keeps transport payloads out of the service API.
type CreateUserInput struct {
	Name  string
	Email string
}

// Service owns user validation, persistence, and post-save event publication as one explicit workflow.
type Service struct {
	repo       UserRepository
	userEvents UserEvents
}

// NewService requires persistence and event collaborators because creation is incomplete without either boundary.
func NewService(repo UserRepository, userEvents UserEvents) *Service {
	return &Service{
		repo:       repo,
		userEvents: userEvents,
	}
}

// Find rejects an empty identifier before asking the repository for application state.
func (s *Service) Find(ctx context.Context, id string) (User, error) {
	if id == "" {
		return User{}, ErrUserNotFound
	}

	return s.repo.Find(ctx, id)
}

// Create publishes only after persistence succeeds so subscribers never observe an unsaved user.
func (s *Service) Create(ctx context.Context, input CreateUserInput) (User, error) {
	name := strings.TrimSpace(input.Name)
	if name == "" {
		return User{}, ErrNameRequired
	}

	email := strings.TrimSpace(input.Email)
	if email == "" {
		return User{}, ErrEmailRequired
	}

	user, err := s.repo.Save(ctx, User{
		Name:  name,
		Email: email,
	})
	if err != nil {
		return User{}, fmt.Errorf("save user: %w", err)
	}

	if err := s.userEvents.PublishCreated(ctx, user); err != nil {
		return User{}, fmt.Errorf("publish user created event: %w", err)
	}

	return user, nil
}

Step 6: Add the Notification Handler

Create internal/notifications/service.go.

The notification service owns the application reaction. Event delivery should not become a hidden replacement for explicit service orchestration.

Create or replace internal/notifications/service.go:

// Package notifications owns reactions to application facts without coupling publishers to their effects.
package notifications

import "context"

// Service is the application boundary for reactions that may evolve independently of event delivery.
type Service struct{}

// NewService constructs the reaction boundary that later scenarios can move onto queue-backed work.
func NewService() *Service {
	return &Service{}
}

// HandleUserCreated keeps the subscriber thin while leaving background execution to a queue-backed implementation.
func (s *Service) HandleUserCreated(_ context.Context, _ string, _ string) error {
	return nil
}

Step 7: Add Subscriber Registration

Create internal/notifications/subscribers.go.

Subscribers.Register subscribes to the typed users.created event and delegates through UserCreatedHandler, keeping transport registration separate from the concrete reaction.

Create or replace internal/notifications/subscribers.go:

// Package notifications owns reactions to application facts without coupling publishers to their effects.
package notifications

import (
	"context"

	"your/module/internal/events"
)

// UserCreatedHandler keeps event delivery independent from the reaction's concrete implementation.
type UserCreatedHandler interface {
	// HandleUserCreated receives the stable identity carried by the application event.
	HandleUserCreated(ctx context.Context, userID string, email string) error
}

// Subscribers owns event registration so subscription lifetime remains part of the App lifecycle.
type Subscribers struct {
	handler UserCreatedHandler
}

// NewSubscribers requires a handler because every received event must have an explicit destination.
func NewSubscribers(handler UserCreatedHandler) *Subscribers {
	return &Subscribers{handler: handler}
}

// Register translates the typed event into the application-facing user-created reaction.
func (s *Subscribers) Register(ctx context.Context, bus events.Bus) (events.Subscription, error) {
	return bus.WithContext(ctx).Subscribe(func(ctx context.Context, event events.UserCreated) error {
		return s.handler.HandleUserCreated(ctx, event.UserID, event.Email)
	})
}

Step 8: Test Subscriber Delivery

Create internal/notifications/subscribers_test.go.

The test publishes through the generated in-process bus and proves the typed event reaches the application handler. It does not start HTTP or the full App runtime.

Create or replace internal/notifications/subscribers_test.go:

// Package notifications verifies typed event delivery without starting the App runtime.
package notifications

import (
	"context"
	"testing"

	"your/module/internal/events"
)

// recordingUserCreatedHandler records the application-facing values delivered by the subscriber.
type recordingUserCreatedHandler struct {
	calls  int
	userID string
	email  string
}

// HandleUserCreated captures one delivery without introducing notification behavior into the subscriber test.
func (handler *recordingUserCreatedHandler) HandleUserCreated(_ context.Context, userID string, email string) error {
	handler.calls++
	handler.userID = userID
	handler.email = email
	return nil
}

// TestSubscribersDeliverUserCreated proves the generated in-process bus reaches the registered application handler.
func TestSubscribersDeliverUserCreated(t *testing.T) {
	ctx := context.Background()
	t.Setenv("EVENTS_DRIVER", "inproc")

	manager, err := events.NewManagerWithContext(ctx)
	if err != nil {
		t.Fatalf("build event manager: %v", err)
	}
	bus := manager.Default()
	if err := bus.Start(ctx); err != nil {
		t.Fatalf("start event bus: %v", err)
	}
	t.Cleanup(func() {
		if err := bus.Close(context.Background()); err != nil {
			t.Errorf("close event bus: %v", err)
		}
	})

	received := &recordingUserCreatedHandler{}
	subscription, err := NewSubscribers(received).Register(ctx, bus)
	if err != nil {
		t.Fatalf("register subscribers: %v", err)
	}
	t.Cleanup(func() {
		if err := subscription.Close(); err != nil {
			t.Errorf("close subscription: %v", err)
		}
	})

	if err := bus.WithContext(ctx).Publish(events.UserCreated{
		UserID: "43",
		Email:  "[email protected]",
	}); err != nil {
		t.Fatalf("publish user created: %v", err)
	}

	if received.calls != 1 {
		t.Fatalf("handler calls = %d, want 1", received.calls)
	}
	if received.userID != "43" {
		t.Fatalf("handler user id = %q, want %q", received.userID, "43")
	}
	if received.email != "[email protected]" {
		t.Fatalf("handler email = %q, want %q", received.email, "[email protected]")
	}
}

Step 9: Register Subscribers in the Lifecycle

Update app/lifecycle.go.

This keeps subscriber registration in the App lifecycle, not in init, package globals, or controller constructors.

Create or replace app/lifecycle.go:

// Package app owns application composition and lifecycle hooks.
package app

import (
	"context"

	"your/module/internal/events"
	"your/module/internal/notifications"
	"your/module/internal/runtime"
)

// LifecycleRegistry keeps subscription ownership aligned with App startup and shutdown ordering.
type LifecycleRegistry struct {
	eventManager             *events.Manager
	notificationSubscribers  *notifications.Subscribers
	notificationSubscription events.Subscription
}

// NewLifecycleRegistry requires the generated event manager and the App's subscriber collection.
func NewLifecycleRegistry(
	eventManager *events.Manager,
	notificationSubscribers *notifications.Subscribers,
) *LifecycleRegistry {
	return &LifecycleRegistry{
		eventManager:            eventManager,
		notificationSubscribers: notificationSubscribers,
	}
}

// Register starts subscriptions after event buses and closes them before those buses shut down.
func (r *LifecycleRegistry) Register(lifecycle *runtime.Lifecycle) {
	lifecycle.On(runtime.Startup, r.Startup)
	lifecycle.On(runtime.Shutdown, r.Shutdown)
}

// Startup retains the subscription handle so shutdown can release the exact registered consumer.
func (r *LifecycleRegistry) Startup(ctx context.Context) error {
	subscription, err := r.notificationSubscribers.Register(ctx, r.eventManager.Default())
	if err != nil {
		return err
	}
	r.notificationSubscription = subscription
	return nil
}

// Shutdown closes the subscriber before the generated lifecycle stops its event bus.
func (r *LifecycleRegistry) Shutdown(_ context.Context) error {
	return r.notificationSubscription.Close()
}

Step 10: Update the Controller

Update internal/users/controller.go so it supports both GET /users/:id and POST /users.

Create or replace internal/users/controller.go:

// Package users keeps user behavior independent from HTTP and infrastructure details.
package users

import (
	"errors"
	"net/http"

	"github.com/goforj/web"
)

// Controller translates HTTP requests into user service calls without owning workflow behavior.
type Controller struct {
	service *Service
}

// createRequest limits the transport payload to fields accepted by the creation workflow.
type createRequest struct {
	Name  string `json:"name"`
	Email string `json:"email"`
}

// NewController requires the service because every route delegates to the application workflow.
func NewController(service *Service) *Controller {
	return &Controller{service: service}
}

// Routes keeps read and creation endpoints discoverable by generated HTTP registration.
func (c *Controller) Routes() []web.Route {
	return []web.Route{
		web.NewRoute(http.MethodGet, "/users/:id", c.Show),
		web.NewRoute(http.MethodPost, "/users", c.Store),
	}
}

// Show maps a missing domain record to HTTP while leaving unexpected failures to middleware.
func (c *Controller) Show(ctx web.Context) error {
	user, err := c.service.Find(ctx.Context(), ctx.Param("id"))
	if errors.Is(err, ErrUserNotFound) {
		return ctx.JSON(http.StatusNotFound, map[string]string{
			"error": "user not found",
		})
	}
	if err != nil {
		return err
	}

	return ctx.JSON(http.StatusOK, user)
}

// Store keeps request decoding and HTTP status mapping outside the user service.
func (c *Controller) Store(ctx web.Context) error {
	var req createRequest
	if err := ctx.Bind(&req); err != nil {
		return ctx.JSON(http.StatusBadRequest, map[string]string{
			"error": "invalid payload",
		})
	}

	user, err := c.service.Create(ctx.Context(), CreateUserInput{
		Name:  req.Name,
		Email: req.Email,
	})
	if errors.Is(err, ErrNameRequired) || errors.Is(err, ErrEmailRequired) {
		return ctx.JSON(http.StatusBadRequest, map[string]string{
			"error": err.Error(),
		})
	}
	if err != nil {
		return err
	}

	return ctx.JSON(http.StatusCreated, user)
}

Step 11: Wire the Event Boundary and Subscriber

Add the event publisher and notification subscriber providers.

Update app/wire/inject_services_app.go so it includes:

"your/module/internal/events"
"your/module/internal/notifications"
"your/module/internal/runtime"

Step 12: Add Event Providers

provideEventBus exposes the generated default event bus to the application publisher. Wire also binds notifications.Service to the handler interface required by subscriber registration.

Update app/wire/inject_services_app.go so it includes:

provideEventBus,
users.NewUserEventPublisher,
wire.Bind(new(users.UserEvents), new(*users.UserEventPublisher)),
users.NewService,
notifications.NewService,
wire.Bind(new(notifications.UserCreatedHandler), new(*notifications.Service)),
notifications.NewSubscribers,

Step 13: Add the Event Bus Provider

Wire can now satisfy users.NewUserEventPublisher.

Update app/wire/inject_services_app.go so it includes:

// provideEventBus exposes the default generated bus without coupling the publisher to its manager.
func provideEventBus(manager *events.Manager) events.Bus {
        return manager.Default()
}

// provideUserRepository preserves the service boundary while Wire composes its concrete cache-aside implementation.
func provideUserRepository(source *users.MemoryUserRepository, profileCache *cache.Cache) users.UserRepository {

Step 14: Update the Service Test

The test uses a small event boundary fake. It does not need to start the event bus or the App runtime.

Create or replace internal/users/service_test.go:

// Package users keeps user behavior independent from HTTP and infrastructure details.
package users

import (
	"context"
	"testing"

	"github.com/goforj/cache"
)

// recordingUserEvents records published users so service tests stay independent of event runtime startup.
type recordingUserEvents struct {
	created []User
}

// PublishCreated captures the application fact without introducing transport behavior into the service test.
func (r *recordingUserEvents) PublishCreated(_ context.Context, user User) error {
	r.created = append(r.created, user)
	return nil
}

// newTestService keeps repository construction consistent while each test controls its event collaborator.
func newTestService(ctx context.Context, userEvents UserEvents) *Service {
	source := NewMemoryUserRepository()
	profileCache := cache.NewCache(cache.NewMemoryStore(ctx))
	return NewService(NewCachedUserRepository(source, profileCache), userEvents)
}

// TestServiceFindsUser preserves the synchronous profile lookup while creation gains event publication.
func TestServiceFindsUser(t *testing.T) {
	ctx := context.Background()
	service := newTestService(ctx, &recordingUserEvents{})

	user, err := service.Find(ctx, "42")
	if err != nil {
		t.Fatalf("find user: %v", err)
	}
	if user.ID != "42" {
		t.Fatalf("user id = %q, want %q", user.ID, "42")
	}
}

// TestServicePublishesUserCreatedEvent proves persistence completes before one typed fact leaves the workflow.
func TestServicePublishesUserCreatedEvent(t *testing.T) {
	ctx := context.Background()
	published := &recordingUserEvents{}
	service := newTestService(ctx, published)

	user, err := service.Create(ctx, CreateUserInput{
		Name:  "Grace Hopper",
		Email: "[email protected]",
	})
	if err != nil {
		t.Fatalf("create user: %v", err)
	}
	if user.ID == "" {
		t.Fatal("expected saved user id")
	}
	if len(published.created) != 1 {
		t.Fatalf("created events = %d, want 1", len(published.created))
	}

	created := published.created[0]
	if created.ID != user.ID {
		t.Fatalf("created event user id = %q, want %q", created.ID, user.ID)
	}
	if created.Email != "[email protected]" {
		t.Fatalf("created event email = %q, want %q", created.Email, "[email protected]")
	}
}

// TestServiceRejectsEmptyID proves invalid lookup state does not reach injected dependencies.
func TestServiceRejectsEmptyID(t *testing.T) {
	ctx := context.Background()
	service := newTestService(ctx, &recordingUserEvents{})

	_, err := service.Find(ctx, "")
	if err == nil {
		t.Fatal("expected error")
	}
}

Step 15: Test User Route Registration

Create internal/users/controller_test.go.

This focused contract test prevents the inherited GET route from hiding an accidental loss of the user creation route.

Create or replace internal/users/controller_test.go:

// Package users verifies the feature's HTTP contract without starting the HTTP runtime.
package users

import (
	"context"
	"net/http"
	"testing"
)

// TestControllerRoutesIncludeUserCreation protects the method and feature-local path used by App route registration.
func TestControllerRoutesIncludeUserCreation(t *testing.T) {
	controller := NewController(newTestService(context.Background(), &recordingUserEvents{}))

	for _, route := range controller.Routes() {
		if route.Method() == http.MethodPost && route.Path() == "/users" {
			return
		}
	}

	t.Fatal("POST /users route is not registered")
}

Build and Verify

bash

forj build

bash

go test ./...

bash

forj route:list

Expected output includes:

text

/api/v1/users

Try the Route

Run the HTTP server:

bash

forj api

Create a user:

bash

curl -X POST http://localhost:3000/api/v1/users \
  -H 'Content-Type: application/json' \
  -d '{"name":"Grace Hopper","email":"[email protected]"}'

Expected response:

json

{"id":"43","name":"Grace Hopper","email":"[email protected]"}

The service saved the user, published users.created, and the lifecycle-registered subscriber handled the event.

Operations

Operational notes:

inproc is process-local and non-durable, which is useful for local same-process reactions.
Use a distributed event driver when events must cross process boundaries.
Use a queue and job when work needs retries, delay, timeout, worker lifecycle, or operational replay.
Published events and subscriber deliveries can appear in metrics, inspect records, Lighthouse runtime views, and driver configuration.

Swap the Driver

To publish through Redis in production, compile Redis event support and select it:

dotenv

EVENTS_SUPPORTED_DRIVERS=inproc,redis
EVENTS_DRIVER=redis
EVENTS_ADDR=redis:6379

Then run:

bash

forj build

Business code does not change. The service still publishes through UserEvents, and the subscriber still registers against the generated bus.

Common Mistakes

Common mistakes

Do not use events as a substitute for durable background jobs.
Do not register subscribers in package init functions.
Do not publish from controllers when the service owns the workflow.
Do not put full user records, tokens, or request payloads in events.
Do not assume inproc events are visible across processes.
Do not hide critical business workflows only inside subscribers.

Next Steps

Next, dispatch queue-backed work from an event subscriber with Reports Generate Job.

Users Created Event ​

What You Will Build ​

Prerequisites ​

Golden Path State ​

Files ​

Step 1: Refresh Event Resources ​

Step 2: Add the Event ​

Step 3: Extend the Repository ​

Step 4: Add an Event Publisher Boundary ​

Step 5: Publish from the Service ​

Step 6: Add the Notification Handler ​

Step 7: Add Subscriber Registration ​

Step 8: Test Subscriber Delivery ​

Step 9: Register Subscribers in the Lifecycle ​

Step 10: Update the Controller ​

Step 11: Wire the Event Boundary and Subscriber ​

Step 12: Add Event Providers ​

Step 13: Add the Event Bus Provider ​

Step 14: Update the Service Test ​

Step 15: Test User Route Registration ​

Build and Verify ​

Try the Route ​

Operations ​

Swap the Driver ​

Common Mistakes ​

Next Steps ​

Users Created Event

What You Will Build

Prerequisites

Golden Path State

Files

Step 1: Refresh Event Resources

Step 2: Add the Event

Step 3: Extend the Repository

Step 4: Add an Event Publisher Boundary

Step 5: Publish from the Service

Step 6: Add the Notification Handler

Step 7: Add Subscriber Registration

Step 8: Test Subscriber Delivery

Step 9: Register Subscribers in the Lifecycle

Step 10: Update the Controller

Step 11: Wire the Event Boundary and Subscriber

Step 12: Add Event Providers

Step 13: Add the Event Bus Provider

Step 14: Update the Service Test

Step 15: Test User Route Registration

Build and Verify

Try the Route

Operations

Swap the Driver

Common Mistakes

Next Steps