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 strategyHow to start experimenting with controlled failure locally, before it happens in the wildReal-world examples of chaos experiments that catch bugs you'd never find in traditional testingTools and techniques to get started without blowing up your infrastructureThrough 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.

Multi-account and multi-region compatibility enables users to manage and deploy resources across multiple AWS accounts and geographic regions. This functionality enhances the robustness of the deployments by offering improved fault tolerance, scalability, and regulatory compliance. By segregating resources into separate accounts and distributing them across various regions, users can minimize the impact of potential failures and optimize performance.In this session from LocalStack Community Meetup May '24, Sannya Singhal discussed how you could use LocalStack to emulate multi-account and multi-region environments locally for testing and development purposes, ensuring that applications were resilient and scalable before deployment to the cloud.

LocalStack’s core cloud emulator allows us to run our own cloud application - including its infrastructure - locally, which provides an efficient developer experience at the start of the entire software development lifecycle (SDLC). This experience enables us to build our product features in a way that closely matches what our customers are looking for — a comprehensive developer platform that facilitates local multi-cloud development across different providers and services.In this session from LocalStack Community Meetup April '24, Lukas Pichler showcases how to use the LocalStack core cloud emulator and other novel solutions, to build, test, and integrate new features in our LocalStack Web Application. He broadly discusses:• Application Overview• How do we enable local cloud development?How do we use LocalStack in CI?• How do we use LocalStack to enable application previews and E2E testing?• Conclusion

AWS Database Migration Service provides migration solutions from databases, data warehouses, and other types of data stores (e.g. S3, SAP). The migration can be homogeneous (source and target have the same type), but often is heterogeneous as it supports migration from various sources to various targets (self-hosted and AWS services).LocalStack supports DMS with selected use cases. In this session from LocalStack Community Meetup July '24, Mathieu Cloutier explores how to use LocalStack to migrate from a MariaDB database to an AWS Kinesis Stream. He goes over the differences between CDC and full load, and as a bonus you will see how easy it is to migrate from an external database to your Kinesis Stream — tested all on your local machine!Docs: https://docs.localstack.cloud/user-guide/aws/dms/