26 docs tagged with "service:bff"

Goal: register a new legacy C# service behind /api/v1/proxy/.

The problem a BFF solves

This is the business‑level overview of the EmpowerNow BFF (Backend for Frontend). Use it to explain the value to non‑technical stakeholders and why we standardized on this pattern.

Summary

ARIA AI Agent Proxied Policy Enforcement

Use this visual guide to explain the BFF to any audience in minutes. Each diagram is presentable as a slide; keep this page open during your talk.

Goal: call an EmpowerID WebUI API method through the BFF.

Budgets

Overview

Purpose: call EmpowerID workflows and WebUI API directly via the BFF with OAuth token injection and PDP-aware context.

Steps

Purpose: operator endpoints for liveness/readiness and Prometheus metrics.

Purpose: route IdP admin API calls through the BFF with session enforcement and token injection.

Purpose: stable façade to legacy C# microservices with circuit breaker, caching, limits, and metrics.

Environment

Policy examples

Prerequisites

Observability

Use LLMPRICINGJSON or LLMPRICINGPATH to override pricing used for estimates during routing.

Purpose: map API paths/methods to resource/action with optional id extraction to build PDP context.

Goal: execute a configured EmpowerID workflow through the BFF.

Goal: harden /api/v1/admin/* routes proxied to IdP.

Purpose: stream Server‑Sent Events from CRUD service through the BFF.

Goal: adjust circuit breaker and caching behavior for legacy proxy.

Goal: fix broken SPA calls after service renames, path changes, or config moves.

Source of truth: ServiceConfigs/BFF/config/routes.yaml (mounted to /app/config).