<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/sources/flydotio/best-of/2024" -->

---
title: Best Fly.io posts of 2024 | daily.dev
description: The most upvoted Fly.io posts of 2024, curated by the daily.dev community.
canonical: https://daily.dev/sources/flydotio/best-of/2024
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:url: https://daily.dev/sources/flydotio/best-of/2024
og:type: website
og:site_name: daily.dev
og:title: Best Fly.io posts of 2024 | daily.dev
og:description: The most upvoted Fly.io posts of 2024, curated by the daily.dev community.
og:image: https://media.daily.dev/image/upload/s--VAY5ToZt--/f_auto/v1724209435/public/daily.dev%20-%20open%20graph
---

# Best of Fly.io — 2024

1. 1  
[](https://daily.dev/posts/kubernetes-without-nodes-bmbrb9gkl "Kubernetes without nodes")  
Video  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 2y  
Kubernetes without nodes  
Fly Kubernetes allows for a node-less Kubernetes setup using a combination of a trimmed-down Kubernetes version called k3s for the control plane and Virtual kuet, which emulates traditional kubelet behavior. Instead of worker nodes, Fly uses virtual nodes and its own machines API to manage pods and orchestration. This decentralized approach offloads scheduling decisions to Fly’s own orchestrator, leveraging high availability and self-managed physical machines.  
26  
1
2. 2  
[](https://daily.dev/posts/do-you-really-need-kubernetes--a0n9cjzsj "Do you REALLY need Kubernetes?")  
Video  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 2y  
Do you REALLY need Kubernetes?  
Kubernetes is not always necessary for startups, and they often reach for it prematurely due to misconceptions. Orchestration, fundamentally about managing multiple containers across physical machines, can be achieved without Kubernetes. Kubernetes offers benefits like a common, cloud-agnostic language and declarative management, making sense for complex, large-scale applications. However, simpler alternatives can handle orchestration tasks, and startups should carefully consider their real needs before adopting Kubernetes.  
23  
2
3. 3  
[](https://daily.dev/posts/ai-gpu-clusters-from-your-laptop-with-livebook-ntealblso "AI GPU Clusters, From Your Laptop, With Livebook")  
Article  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 2y  
AI GPU Clusters, From Your Laptop, With Livebook  
Livebook, FLAME, and the Nx stack are powerful components in the Elixir ecosystem that enhance data computation and serverless computing. Livebook integrates closely with Elixir app clusters for seamless local and remote compute, while FLAME manages serverless executors for scalable application performance. The Nx stack supports Elixir-native AI and ML, allowing complex computations with GPU backends. Recent demonstrations at ElixirConf 2024 highlighted their capabilities, including real-time hyperparameter tuning on remote GPUs, made possible by Fly.io's infrastructure.  
17
4. 4  
[](https://daily.dev/posts/gpus-on-fly-io-are-open-for-everyone--5npxah1nf "GPUs on Fly.io are open for everyone!")  
Article  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 3y  
GPUs on Fly.io are open for everyone!  
Fly.io has made GPUs available to everyone, allowing users to spin up GPU instances for tasks such as large language model inferencing and image generation. The available GPU types are Ampere A100 (40GB), Ampere A100 (80GB), and Lovelace L40s (48GB). The post also mentions that lower-cost A10 GPUs will be introduced in the future. Additional articles related to using GPUs on Fly.io are provided for further exploration.  
17  
1
5. 5  
[](https://daily.dev/posts/we-don-t-use-containers-and-here-s-why--mo9qd5txe "We don't use containers, and here's why.")  
Video  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 2y  
We don't use containers, and here's why.  
11  
3
6. 6  
[](https://daily.dev/posts/we-use-containers-now-here-s-why--rrak8nbdx "We use containers now. Here's why.")  
Video  
![Avatar of flydotio](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/deb71e3b6f964388876ecc82c26c8f6c)Fly.io · 2y  
We use containers now. Here's why.  
Fly.io now supports running containers inside fly machines, a shift from their previous method of unpacking Docker images directly onto lightweight virtual machines. This change, driven by the need for sidecar containers in their managed Kubernetes service, improves flexibility and allows for tighter coupling of services. Fly machines use a combination of Firecracker hypervisor and the pilot init process to manage containers, making it possible to deploy and manage multiple images separately within a single virtual machine.  
10

[See all Fly.io archives](/sources/flydotio/best-of)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@graph":[{"@type":"CollectionPage","@id":"https://daily.dev/sources/flydotio/best-of/2024#page","url":"https://daily.dev/sources/flydotio/best-of/2024","name":"Best Fly.io Posts of 2024","description":"The most upvoted Fly.io posts of 2024, curated by the daily.dev community.","isPartOf":{"@type":"WebSite","url":"https://daily.dev"}},{"@type":"ItemList","@id":"https://daily.dev/sources/flydotio/best-of/2024#items","numberOfItems":6,"itemListElement":[{"@type":"ListItem","position":1,"url":"https://daily.dev/posts/kubernetes-without-nodes-bmbrb9gkl","name":"Kubernetes without nodes"},{"@type":"ListItem","position":2,"url":"https://daily.dev/posts/do-you-really-need-kubernetes--a0n9cjzsj","name":"Do you REALLY need Kubernetes?"},{"@type":"ListItem","position":3,"url":"https://daily.dev/posts/ai-gpu-clusters-from-your-laptop-with-livebook-ntealblso","name":"AI GPU Clusters, From Your Laptop, With Livebook"},{"@type":"ListItem","position":4,"url":"https://daily.dev/posts/gpus-on-fly-io-are-open-for-everyone--5npxah1nf","name":"GPUs on Fly.io are open for everyone!"},{"@type":"ListItem","position":5,"url":"https://daily.dev/posts/we-don-t-use-containers-and-here-s-why--mo9qd5txe","name":"We don't use containers, and here's why."},{"@type":"ListItem","position":6,"url":"https://daily.dev/posts/we-use-containers-now-here-s-why--rrak8nbdx","name":"We use containers now. Here's why."}]},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Sources","item":"https://daily.dev/sources"},{"@type":"ListItem","position":3,"name":"Fly.io","item":"https://daily.dev/sources/flydotio"},{"@type":"ListItem","position":4,"name":"Best of","item":"https://daily.dev/sources/flydotio/best-of"},{"@type":"ListItem","position":5,"name":"2024"}]}]}
```

