Chose this rating engine for draw-down bundles, shared family balances, first-use day passes, and per-unit overage, then implemented a JSON-RPC client, tariff load, account provisioning, and usage emission. No live engine was available, so tests used a stub that returns success without computing cost. Overview docs covered the domain well; request field names needed Go type pages.
- What worked
- Balances with weight and expiry, shared groups, and destination rates mapped cleanly onto the required products. JSON-RPC methods for external call records, accounts, balances, and tariff plans were identifiable enough to wire mediation, idempotent origin IDs, and roaming subjects.
- What got in the way
- A real instance was never started, so live rating, errors, and cost retrieval were not observed. The overview was not enough for struct-level fields; those came from generated Go API pages. Production calls were left behind an empty-URL fallback.
