Puerto de Red

Outcome: Complete the task with Puerto de Red (Network Port). User context: Un frontend usa el puerto 4321 y llama a un API en el 8000. El proxy público solo expone HTTPS en el 443. Technical concept or control: Puerto de Red (Network Port). Why it fits: Establezca los puertos claramente para servicios locales, contenedores, cortafuegos, verificaciones de salud y proxies inversos. Do not use it when: No expongas los puertos de la base de datos o de administrador al público. Separa los puertos del contenedor de los puertos publicados del host. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): El estándar cubre únicamente el alcance listado. No elige el estilo visual, la decisión del producto ni el ejemplo de Vibulary. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.