Thanks for the kind words. And don't worry - we an...
# http4k
d
Thanks for the kind words. And don't worry - we and Http4k are not going anywhere 🙃. But that said, trying to model your code so you’re not too shackled to a particular lib is good practice, so try and structure your app so that the transport code is in one layer and your biz logic in another. Then if you ever have to switch us out, you can just port the routing layer. Luckily, because of the SaaF model, the reusability of the test contracts would allow you to keep your tests even if you decided to use something else. If we ever do a marketing campaign, we’ll probably go with the strapline “use Http4k: it’s really easy to throw away” 😆
😂 1