Replies: 1 comment
-
That's right. The "sidecar" buildpack approach is one way. We need to make Heroku buildpack, though, which we haven't yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was wondering what the best practices are to use edgedb on Heroku. I didn't see any notes here as to how to do so.
Given my understanding of the edgedb architecture, it seems like the
application -> edgedb -> postgres
in which case edgedb should be runnable as a sort of sidecar / daemon process sitting along side the application and then communicating with a standard (managed) DB service. In that case perhaps using a similar approach to how Heroku suggests integrating pgbouncer with your application which is to use "Multiple Buildpacks for an App" and then run theedgedb
application as a daemon process in the same dyno as the webserver. I don't know the implications though of having multiple daemons running in different dynos.Beta Was this translation helpful? Give feedback.
All reactions