Rethinking Serverless with Flame

1. temporal

   1 19 14,024 9.9 Go

   Temporal service

   

   I don't know if I agree with the argument regarding durability vs elastic execution. If I can get both (with a nice API/DX) via something like Temporal (https://github.com/temporalio/temporal), what's the drawback here?

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. basic-examples

   2 1 4 10.0 Python

   Contains source code for the basic examples in the PiCloud Documentation.

   

   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?

4. libcluster_postgres

   3 3 219 3.3 Elixir

   Postgres strategy for libcluster

   

   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

5. flame

   4 4 1,073 8.1 Elixir

   Fleeting Lambda Application for Modular Execution: auto scale parts of your existing app with a single function call (by phoenixframework)

   

   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...

6. sst

   5 195 23,676 9.9 TypeScript

   Build full-stack apps on your own infrastructure.

   

   I think the casing is not enforced by HN but rather up to the poster?

   > (Aside: I wish someone would rethink Serverless, heh.)

   Not sure if you've checked out https://sst.dev/ but I think they've done precisely that. For example, they have Live Lambda Development which makes local dev a real breeze by significantly shortening feedback loops (no need to push your code up to the cloud and wait for it to deploy)

7. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

Suggest a related project