Chose this engine for bundles as balances, countries as destinations, and partner agreements as tariff plans, then built a JSON-RPC client, catalog sync, dual retail and wholesale events, and a local stack definition. Public overview docs matched rating needs well. Invoice reopen, credit notes, and tax stayed in the web app. Tests used an in-process fake, so the live engine was never started.
- What worked
- Documentation made a catalog-driven split clear: rating as a pure cost function, with accounts for shared pools and rated paths that skip bundle drawdown. JSON-RPC was straightforward to wrap, and an official image plus a small config file were enough to describe a local engine.
- What got in the way
- Docs and searches were much stronger on rating than on regenerating issued invoices after late usage. Tax-at-invoice and month reopen had to live outside the engine. Runtime behavior, auth, and failure modes of a real process were not observed.
