Ever wonder why some teams intentionally break their own systems? Welcome to the world of chaos engineering — a practice that's not just for Netflix-scale infrastructure, but for any team that wants to build resilient, reliable applications. In this session, we'll demystify chaos engineering and explain why intentionally breaking things is actually the smart move. You'll learn what chaos engineering really is (in plain English, no buzzwords), why waiting for production failures is a terrible strategy, how to start experimenting with controlled failure locally, before it happens in the wild, real-world examples of chaos experiments that catch bugs you'd never find in traditional testing, and tools and techniques to get started without blowing up your infrastructure. Through practical demos using LocalStack's cloud emulation and chaos engineering tools, we'll simulate failures like network latency, service outages, and resource exhaustion right from your laptop. If you've ever said "it worked on my machine" only to watch it crash in production, this talk is for you—let's break things intentionally so they don't break unexpectedly.

Connecting your applications to LocalStack has not always been easy. In this video, Simon from the LocalStack team discusses how we streamlined the LocalStack networking experience. We discussed the challenges of connecting your applications to LocalStack and how we're simplifying the LocalStack networking experience. Simon also discussed about configurations required for more complex networking setups, and some common networking scenarios, with example configuration for achieving connectivity.

LocalStack integrates with official AWS Software Development Kits (SDKs) so you can connect to LocalStack services using the same application code you use for AWS services. This lets you develop and test your applications locally without connecting to the cloud. In this video, we will talk about how you can connect to LocalStack emulated services using AWS SDKs.

LocalStack is ephemeral, so when you stop and restart it, all data is lost. You can use certain features to save the state & load it back when you restart LocalStack. This includes saving the local state for S3 buckets, DynamoDB tables, RDS databases and more. In this video, we explore three mechanisms that allow you to save state in LocalStack: persistence, state export and import, and Cloud Pods.