Serverless With Servers? FLAME is...weird

I'm a big fan of serverless. It has negatives though. Really hyped Fly is exploring other options. Not sure how I feel about them just yet

S/O Ph4se0n3 for the awesome edit 🙏

[LusidDreaming]

I've been working on a mostly serverless application for about 8 months now, and at this point I'm tired of hearing about "no more servers or containers to manage." I honestly miss containers at this point. It seems like its going to be a lot more simple and easier to maintain, but my experience has been that you are just trading one set of complexities for another.

[mbst]

I just started learning elixir last week, because I couldn’t believe the amount of work required to have scaling background jobs etc in JS land. And Im baffled at how many problems just don’t exist in the space - or are solved WAY more elegantly. FLAME is like the icing on this delicious cake.

[runtimejpp]

tried elixir after the Jose interview and it seemed super tough, The pattern matching is a new concept to me but the potential seemed limitless. Props to elixir devs

[slobodan-milosevic]

7:28 thats a fair take, its also what makes elixir and erlang world so great because you could have a machine running some elixir or erlang code to maintain and give database connections from a pool and as long as your lambda is running on the same network or cluster, you don't need to worry about it that much

[FzsHotDogInDonut]

I have only one problem with all of these solutions. They do not provide localized price for devs from Bangladesh or nearby countries. How am I supposed to pay 25$ a month when I made only 200$ for entire project.

[elodens]

if its creating a copy of the app to run the generate_thumbnail function, why couldnt they just auto scale and load balance the original app to begin with? Seems like cart before horse.

[Exilum]

I do think it's very cool, but on the other hand it only really matters when you app is already at a big scale. I'm happy with my nextjs docker container spun in google cloud run.

[slobodan-milosevic]

I'm very excited about this, this makes me think about several ideas to build along with axon

[amanrv]

My take is that this couples an abstracted version of infra with your code. That might be acceptable in some scenarios but not most. In any case if your app is not used by hundreds of millions of users, you'll get far with a monolith, so most people don't need to solve this problem anyway.

[antonioss]

found your twitter first and thought it sucked pretty bad, then found your channel and you know what, i think it got me turned around

[ujames]

how about using kafka as a queue system with upstash?

[Bennigames]

So you integrate this magic and then 5 years down the line when they decide to hike prices or change the api you have major problems. Yeah idk I think I will just spin up a new docker container on any provider of my choice instead if I need more processing power and invest a bit more engineering effort upfront

[aleattorium]

Everyone considering this has to remember one point: this is beta / 1.0.
Let's keep watching this space, but it really is interesting.

[atulkumar_zip]

Im having problem in t3-stsck im using app router version yesterday it work fine but now it giving : Error querying the database: FATAL: remaining connection slots are reserved for non-replication superuser connections


But i set max connections to 300 what i do?

[boenrobot]

What's the difference between FLAME and just... forking a process?

[plexq]

Seems to have a bit of similarity to how Apache Spark was conceived, but for javascript... I think that part is actually really interesting... I've done a lot of stuff with spark, and having good bindings for something like that but with the Javascript runtime would be interesting. Not sure those CPU bound use cases are a really good fit for the JS runtime though?

[jackfrosch]

If the Lambda 15-minute timeout is too limiting for a use case, consider using Fargate as a scale-to-zero, serverless option for longer running tasks. It's billed for a minimum one minute and per-second granularity versus Lambda's millisecond billing, so you may not want to use it for <15min workloads.

Re: DB connections. Connection pooling is a must with serverless. Many serverless DBs (e.g. CockroachDB, Neon DB) provide connection pooling.

[omarmihilmy]

You can use an ECS Task for the chunky tasks

[stefankyriacou]

The best solution i've seen as a complement to serverless functions that simplifies infrastructure is temporal.

[bravethomasyt]

I don't think you'd use this for an API, you'd use this for when you need to process something and the server load for it is spiky or unpredictable. But honestly, it's great.