flame
libcluster_postgres
flame | libcluster_postgres | |
---|---|---|
1 | 3 | |
694 | 178 | |
13.3% | 3.4% | |
8.7 | 6.7 | |
23 days ago | 4 months ago | |
Elixir | Elixir | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flame
-
Rethinking Serverless with Flame
Probably not too much to say that’s specific to FLAME. Closures are serializable and can be sent as messages to actors on the BEAM.
From a quick look at the code, this looks the magic line: https://github.com/phoenixframework/flame/blob/main/lib/flam...
libcluster_postgres
-
Elixir clustering using Postgres
However, when it comes to connecting the servers, there seems to be a barrier of entry that many people encounter, including ourselves, on how to provide the name discovery required to connect said servers. We have released our approach to solving this problem by open-sourcing libcluster Postgres Strategy and today, we explore the motivations behind its creation and the methodologies employed in its development.
-
Rethinking Serverless with Flame
Ah, that makes a lot of sense - I think the FLAME.Parent{} approach may enable backends that wouldn't be possible otherwise.
For example, if I used the heroku api to do the equivalent of ps:scale to boot up more nodes - those new nodes (dynos in heroku parlance) could see what kind of pool members they are. I don't think there is a way to do dyno specific env vars - they apply at the app level.
If anyone tries to do a Heroku backend before I do, an alternative might be to use distinct process types in the Procfile for each named pool and ps:scale those to 0 or more.
Also, might need something like Supabase's libcluster_postgres[1] to fully pull it off.
[1] https://github.com/supabase/libcluster_postgres
- Show HN: Libcluster Postgres Strategy for Elixir
What are some alternatives?
sst - Build modern full-stack applications on AWS
libcluster_postgres - Postgres strategy for libcluster
basic-examples - Contains source code for the basic examples in the PiCloud Documentation.