Requests made with HTTPoison are passed to the library’s own connection pool whereas requests made with Mint are handled in the same process. While HTTPoison is great for most use cases, Mint is a promising solution for anyone who has specific control flow requirements.

I’m interested in this for some of the uglier API integrations I maintain where an ordered chain of requests must be made with no guarantee of delivery and responses that involve a considerable amount of in-memory processing (large XML bodies to be exact). Having control over my process architecture is preferable to leaving it up to the HTTP library’s connection pool in these cases.

The main thing is a processless architecture that lets you easily build architectures that are fine-tailored for your use case. You might build a process that holds many connection structs, or a use the connections directly in say a GenStage producer/consumer, or things like those. The idea is that you now have the building blocks to build whatever fits your thing :)