--- title: "Rethinking Serverless with FLAME" url: https://daily.dev/posts/rethinking-serverless-with-flame-4yxnopx8o source_url: https://fly.io/blog/rethinking-serverless-with-flame/ type: article source: "Fly.io" published: 2023-12-06T11:40:18.124Z updated: 2023-12-06T11:40:15.617Z tags: ["backend", "serverless", "elixir"] reading_time: 13 upvotes: 24 comments: 2 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Rethinking Serverless with FLAME **[Fly.io](https://daily.dev/sources/flydotio)** · 13 min read · 24 upvotes · 2 comments ## Summary FLAME is a pattern for elastically scaling applications without the need to manage servers or rewrite the entire application. It allows you to wrap existing app code in a function and run it in a temporary copy of your app. FLAME can be implemented in different languages, but the Elixir flame library is specifically mentioned in the article. The library includes features like process placement and remote monitoring to handle pool scale-up and scale-down logic and to optimize resource usage. FLAME removes the complexities and layers of communication associated with traditional FaaS solutions. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@idoshamun** · 2 upvotes > omg this is insane! they're trying to over the cloud with elixir. They got it all there. The most feature-rich monolithic framework I guess **@dagelf** · 0 upvotes > "With FLAME, you treat your entire application as a lambda, where modular parts can be executed on short-lived infrastructure." ... > > Erm, except that you still have to wrap the functions yourself... and set up the pools. But it's just a handful of lines of code, and you can reuse existing code. > > Its cute. But I don't see why you can't just do this with any code...? FLAME seems to just be a generic server that gets deployed, and called by your program... neat idea. ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments - [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments - [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#serverless](https://daily.dev/tags/serverless), [#elixir](https://daily.dev/tags/elixir) [View this post on daily.dev](https://daily.dev/posts/rethinking-serverless-with-flame-4yxnopx8o)