Gateway/Adapter Pattern & Extensions.

[akil-rails]

background context

I've a situation, where my app (its a bank account opening app), needs to work with different bank's , each having it's own custom api implementation for the same use case - for example, in the app, i've to validate the tax-id ; as far as the app's concerned, it's the same use case (pass in the details of the tax-id, the application), and get back a result (valid/invalid); the api's of each bank have completely different shapes , but can be used to do the same job.. This is the text-book example of the gateway / adapter pattern.

quarkus

in a quarkus implementation, i am wondering if extensions is good use case for this -

1. create one extension per bank
2. depending on the installation, compile the app with the appropriate extension and ship it.
3. there are 70+ such use cases (& will grow over time), so probably create multiple extensions per bank (1 per use case or 1 per bounded context) for easier maintenance.

the interfaces themselves, could be packaged in a simple jar that every extension & the app depends on..

Is this a sound idea or are there simpler / better alternatives