31. Component and Service Governance

The Problem

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

The React Difficulty

React itself does not govern backend-service access by component path. Organizations generally enforce this through conventions, repositories, gateways, linting, and application infrastructure.

React Approach

// Application convention / tooling decides which client may call which API.
const response = await inventoryApi.get("/items");

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.