31. Component and Service Governance

The Problem

Large micro-frontend teams need rules defining which components may access which backend services.

The Angular Difficulty

Angular can govern access through services, guards, and DI, but mapping individual components to backend service permissions is usually application architecture.

Angular Approach

// Service access is usually controlled through Angular services,
// route guards, DI and application conventions.
constructor(private inventory: InventoryApiService) {}

MS Approach

ManySet provides a direct runtime-oriented approach for this recurring business-application task.

// GlobalConfig.json can explicitly map components to services and
// declare AllowedComponents for each service.
// Example: ./Inventory/ -> Inventory.

Why this way is useful in business applications :

The comparison is intended to show where ManySet supplies a business-application abstraction around a recurring task, while keeping HTML and JavaScript visible and directly usable.

Key Point :

ManySet reduces the amount of framework-specific composition required for this particular task, without requiring the React/Angular mechanism to be represented as inherently wrong or incapable.