camcaine
Just played with Mint for an hour. It’s really nice 
Thats it, that’s the whole post.
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
thojanssens1
Also have a look at Finch, built on top of Mint and NimblePool by @keathley
brightball
I wish there was a Tesla adapter for Finch. Would make it easier to try it against other options.
keathley
I believe there’s an open issue for a Tesla adapter. You might see if anyone is making progress on it. Happy to provide a review or guidance if that’s helpful.
camcaine
Curious about this line in the NimblePool readme:
Whats the main reason(s)?
ityonemo
I’m guessing it’s because when you are multiplexing by definition you have a shared resource (the multiplexed channel), where you will then need to figure out how to handle access contention between your pool workers, liable to be a pain in the rear, inducing performance bottlenecks, and also, very likely error prone, even in a safe system like BEAM.
If I’m not mistaken, that’s not saying that you can’t “meta-pool”, that is - You could probably do one-pool-worker-per-channel and have the worker do the demuxing and handling of each multiplexed resource within the channel. You just have to think carefully about what the domain intrinsics are and how those partition into pool workers.
keathley
This is correct. This is why Finch’s http/1.1 and http/2 “pool” implementations are completely different, and why the user is required to specify which they want up front.
minhajuddin
Mint is really nice, I did a few blog posts about it last year: https://scoutapm.com/blog/how-to-use-mint-an-awesome-http-library-for-elixir-part-01