Building a New Project That Integrates with Multiple Partners, Part 1

Kakao Pay developed an auto insurance comparison service that lets users compare products from multiple insurance companies at a glance. Given the structural characteristic of needing to fetch information from n partners, the core challenge was efficiently managing each partner's different API specifications and token policies.

To improve the service's maintainability and scalability, the system was designed with service structure, common structure, and individual structure. In particular, the individual structure was used to independently handle requirements that differ from partner to partner.

The key design points are as follows:

• Token management: A TokenManager interface was defined to individually implement each partner's different token expiration and renewal policies.
• Data transformation: Conversion logic was separated to handle the DTO (Data Transfer Object) structures and encryption/decryption policies that vary by partner.
• UseCase implementation: Each partner's business logic is managed individually, minimizing the impact on the existing system when a new partner is added.