Opening up Ports and Adapters Pattern maybe v2

[twilson63]

This is a discussion about opening up the ports and adapters pattern to a more abstract and modify-able system.

When I was working through the process of documenting how one might go about creating their own ports and then building their own adapters, it occurred to me, that the current design would be for the hyper63 project to incorporate the port into the core. And then the port is specified by a string in the configuration

export default {
  ...
  adapters: [
    { port: 'echo', plugins: [x()] }
  ]
}

I think this kind of control may be unnecessary, we could simply allow developers to import the port of their choosing, then the core would wrap the adapter in the port to validate it. A config file might look like this:

import echoPort from 'hyper63-port-echo'
import greetings from 'hyper63-adapter-greetings'

export default {
  app: express,
  adapters: [
    { port: echoPort, plugins: [greetings()] }
  ]
}

Then another thought occurred to me, it might be worth entertaining the idea to make the API a generic pattern

In the app-express it could implement a pattern like this

POST /{port}/{method} -d {body} 

And that endpoint would connect the request to the appropriately loaded port and method

This would keep the focus of the project on the glue code of the client -> app -> ports -> adapters

And observability would be baked in at the app level or a middleware mod.