Microservices Study Portal

How to use it

Conceptually, two everyday tasks for a backend developer:

Adding an endpoint to a service

the persistence in Infrastructure (EF Core), and only the HTTP plumbing in API.

Response DTO, the route in Configure(), and HandleAsync. Remember the route is relative to the global api/v1 prefix.

service's own realm (the realm wall does this for you). Only add AllowAnonymous() if the route is genuinely public (e.g. a public viewer page).

by hand inside the handler.

filter already scopes them to the current tenant; don't write manual TenantId filters and don't bypass the filter without a very good reason.

1. Pick the layer. Put the use-case logic in Application (a handler),
2. Create a FastEndpoints class in the API layer: a Request DTO, a
3. Decide on auth. By default the endpoint requires a valid token from the
4. Add a validator (Validator<TRequest>) for input rules — don't validate
5. Stay tenant-safe. If you query tenant-owned entities, the global query

Publishing (or consuming) an event

publisher and any consumer reference the exact same type. Keep it small and versionable — other services depend on its shape.

and calling Publish(...). Do this after your local work succeeds; don't block waiting for consumers.

IConsumer<TEvent>; the shared Messaging.RabbitMq wiring discovers and registers it on the bus.

subscription status), prefer a guarded internal HTTP call with a shared secret and a cached fail-safe instead of an event.

1. Define the contract as a record in Messaging.Contracts so both the
2. Publish from your handler by injecting MassTransit's IPublishEndpoint
3. Consume (in the interested service) by implementing
4. Ask, don't tell? If you actually need an answer before continuing (like