flame
By phoenixframework
basic-examples
Contains source code for the basic examples in the PiCloud Documentation. (by picloud)
| flame | basic-examples | |
|---|---|---|
| 1 | 1 | |
| 694 | 4 | |
| 15.1% | - | |
| 8.7 | 10.0 | |
| 24 days ago | about 11 years ago | |
| Elixir | Python | |
| MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of flame.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-06.
-
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...
basic-examples
Posts with mentions or reviews of basic-examples.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-06.
-
Rethinking Serverless with Flame
I used a service years ago that did effectively this. PiCloud were sadly absorbed into Dropbox but before that they had exactly this model of fanning out tasks to workers transparently. They would effectively bundle your code and execute it on a worker.
There’s an example here. You’ll see it’s exactly the same model.
https://github.com/picloud/basic-examples/blob/master/exampl...
I’ve not worked with Elixer but I used Erlang a couple of decades back and it appears BEAM hasn’t changed much (fundamentally). My suspicion is that it’s much better suited for this work since it’s a core part of the design. Still, not a totally free lunch because presumably there a chance the primary process crashes while waiting?
What are some alternatives?
When comparing flame and basic-examples you can also consider the following projects:
sst - Build modern full-stack applications on AWS
libcluster_postgres - Postgres strategy for libcluster