hi, about http4k-connect do you see it as a way to interact with big api or you would use it for any internal client of the app. If it's the second, if your app calls multiple different services, would you write a connect for each one or you think is too much overhead ?

I suppose the pattern is applicable throughout the stack, but we've only considered it for external APIs.

They are external API from the application but they are internal in the corporation.

yeah, there's no reason why you wouldn't do it - especially if you have many services which rely on different bits or slices of the API.