Hello NestForge Microservices

Run the example

Example location:

examples/hello-nestforge-microservices

Run it from the repository root:

cargo run -p hello-nestforge-microservices

Example purpose

This example demonstrates NestForge’s transport-neutral microservice layer without requiring HTTP, gRPC, or WebSockets at the edge.

Files included

The example currently includes:

• src/main.rs
• src/app_module.rs
• src/app_config.rs
• src/microservices/mod.rs
• src/microservices/patterns.rs

Recommended reading order

Read the example in this order:

1. src/app_module.rs
2. src/microservices/patterns.rs
3. src/main.rs

What each file does

src/main.rs

Creates a testing module with TestFactory::<AppModule>, resolves the pattern registry, constructs an in-process microservice client, sends a message, emits an event, prints the result, and shuts the module down.

This is important because it demonstrates that the microservice layer is not tied to a specific external server.

src/app_module.rs

Registers:

• AppConfig
• AppPatterns
• EventCounter

and exports them for the microservice runtime.

src/microservices/patterns.rs

Defines:

• GreetingPayload
• EventCounter
• the app.greet message pattern
• the app.bump event pattern

What users learn from this example

• how to define message and event patterns
• how handlers resolve providers from MicroserviceContext
• how to test microservice workflows in-process
• how stateful side effects such as event counters can still use DI-managed providers

What to verify

When the example runs, verify:

1. the testing module builds successfully
2. app.greet returns a JSON payload
3. app.bump updates the event counter
4. the module shuts down cleanly