Microservicelets and Routes
A microservicelet groups a focused application capability. Its routes define public or authenticated experiences without turning navigation structure into a substitute for domain design.
Route Responsibilities
The controller loads trusted context, validates request input, applies authorization, invokes business services, and prepares view data. The pagepart renders the main content. Prepart and postpart files add only the styles or browser behavior required by that route.
Substantial operational features commonly benefit from a landing or register route, a manage route for controlled changes, and an analytics route for evidence and reporting. Not every simple public page needs all three.
URL Guidance
- Prefer readable path segments over operational query strings.
- Use stable opaque identifiers instead of numeric database identifiers.
- Keep workspace context explicit for workspace-scoped experiences.
- Redirect retired public routes to one canonical successor.
- Return a clear setup-required state when an integration is not configured.
Authorization must be enforced by the server even when a navigation link or button is hidden.