threeaccents
"global" gRPC connection in Phoenix app.
I have a Golang gRPC server I need to talk to from my Phoenix app. I was wondering what the best practice is to hold a single connection to the gRPC server for the entire app. Instead of each time having to create a new connection having a single “global” connection. Should I just create a genserver that holds this connection info? Or is there some mechanics in phoenix itself for me to accomplish this? Or just an overall more idiomatic “elixir” way to do this? Thanks!
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
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!"
First 2 of 2 Posts
hauleth
Depending how is the Golang gRPC service written. If it can handle multiple clients at once, then you can take Ecto as an example and create connection pool. This will allow you to run N (where N is size of pool) parallel connections without worry about overflowing the server and time needed for establishing socket connection.
threeaccents
Yea the server can handle multiple connections. So what would you recommend the approach to be? Set up poolboy to handle the connection pooling and then every time I need to speak to the gRPC server grab an instance from poolboy and use that for my service?