Systems | Development | Analytics | API | Testing

Koyeb

10 Reasons Why We Love Firecracker MicroVMs

As we discussed in Firecracker MicroVMs: Lightweight Virtualization for Containers and Serverless Workloads, Firecracker is a lightweight virtual machine monitor (VMM) that uses Linux kernel-based virtual machines (KVM) to provision and manage lightweight virtual machines (VMs), also known as microVMs. Without further ado, here is a list of the top ten reasons why we love Firecracker.

Cloud Computing and Serverless Architectures: What are FaaS and CaaS?

When creating new cloud-native applications, developers need to choose the development and deployment methods that best serves their application's needs and purpose. At the same time, organizations are always looking to optimize their cloud budgets and efficiency. Two popular deployment strategies are Function as a Service (FaaS) and Container as a Service (CaaS). Perhaps you've heard about them!

Firecracker MicroVMs: Lightweight Virtualization for Containers and Serverless Workloads

Deciding whether to run applications in containers or virtual machines used to entail analyzing which trade-offs you could accept in exchange for certain advantages. With Firecracker, we can leverage the benefits of both technologies. In this blog post, we are going to talk about why exactly Firecracker is setting the serverless computing world on fire and what you need to know about this emerging technology.

Escaping GKE gVisor sandboxing using metadata

GKE is a Google Cloud service that offers a managed Kubernetes cluster, the nodes of the clusters are running on Google Cloud VM instances, the control plane and network is fully managed by GKE. GKE offers a sandboxing feature (https://cloud.google.com/kubernetes-engine/docs/concepts/sandbox-pods ), based on gVisor (https://gvisor.dev/docs/ ) it protects the host kernel from untrusted code.