impl-wrapper

To separate business logic from HTTP calls in a TypeScript wrapper, implement an Impl-Client pattern where the Impl acts as a pure delegating façade. Centralize all HTTP communication and error handling in a separate Client.ts file.

The Impl-Client design pattern separates concerns by keeping Impl.ts as a pure delegating wrapper around Client.ts. This ensures no business logic exists in the Impl layer, while standardizing framework methods like metadata() and isSupported() as platform placeholders.

Set up lazy producer wrappers by implementing wrapped Producer APIs that cache and decorate producers without moving logic into the Impl. This keeps the Impl layer pure while managing producer lifecycle separately across modules.

Yes, the Impl-Client wrapper pattern works for monorepos with multiple services. Applying this pattern across services maintains uniform architecture, reduces boilerplate, and enforces consistent separation of concerns between Impl, Client, and Producer layers.

Avoid using a pure delegating façade when your project cannot enforce a strict two-class structure with separate Impl.ts and Client.ts files. The pattern requires platform-driven placeholder methods and falls apart if business logic cannot be fully centralized in the Client.