🔗 My API integration methodology

A common aspect of modern web applications is the need to communicate with other web applications in what is usually referred to as “API integrations”. For example, consider Stripe. Stripe is a payment processor service that handles the complicated parts of accepting payments. If your app is being extended to have a checkout experience for customers, you might integrate with Stripe to accomplish that.

That said, the “how” of implementing API integrations is more of an art than a science. Typically, each team or developer has their own style for integrations, and what follows is my approach, which is largely based on the idea of bounded contexts from Chapter 14 of Domain-Driven Design.

My typical design for an API integration consists of the following parts:

1. Defining how such a service will be utilized in your application’s domain.
2. Wrapping the service API, in its domain.
3. Tying the two together with an adapter module.