
Are Property Graphs living up to the hype? Maybe the model itself is the problem.We made the move from relational databases to graph databases to escape "Join Pain" and model the real world more naturally — but for many engineering teams, that promise has curdled into something worse: the Spaghetti Graph.Complex queries. Ugly workarounds for multi-party relationships. Fragile schemas that shatter with every iteration and become a nightmare to maintain.The good news? The problem isn't your data.In this talk, Joshua Send breaks down why standard Labeled Property Graphs (LPGs) fall short when applied to complex domains — and introduces TypeDB, a strongly-typed database that brings together the connectivity of a graph with the integrity of a relational model.You'll come away understanding:Why LPGs struggle at scale and complexityWhat "Spaghetti Graphs" are and how teams fall into the trapHow TypeDB's type system enforces data integrity without sacrificing flexibilityWhen a strongly-typed graph database is the right tool for the jobWhether you're deep in a graph migration, evaluating database architectures, or just tired of schema chaos — this one's for you.

LocalStack's core cloud emulator lets you emulate various cloud services on your own computer. This means you can develop and test your cloud-based solutions without connecting to a remote cloud.However, there are times when you need to seamlessly switch between your local setup and actual cloud resources, especially in hybrid situations. For instance, you might want to share a database with your local Lambda function or access S3 files stored remotely while running a Glue ETL job locally.With LocalStack's AWS Replicator extension, your local environment can replicate AWS cloud resources at the API level, allowing direct interaction with cloud services. The Replicator extension enables you to forward specific requests from LocalStack to AWS without complex proxy setups, and create test scenarios that involve a mix of local and cloud resources.Check out our tutorial — https://docs.localstack.cloud/tutorials/replicate-aws-resources-localstack-extension/

LocalStack's cloud emulator lets you run Amazon Elastic Container Service (ECS) clusters and tasks on your local computer. It's sometimes useful to mount code from the host filesystem directly into the ECS container. This helps quickly test changes without needing to rebuild and redeploy the ECS Task's Docker image each time.This video explains how to use code mounting with the ECS bind mounts feature. Here are the links to the resources mentioned in the video:• Sample repository: https://github.com/localstack-samples/ecs-code-mounting-python-cdk• LocalStack Docs: https://docs.localstack.cloud/user-guide/aws/ecs/#mounting-local-directories-for-ecs-tasks• AWS Docs: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/bind-mounts.html

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 allows you to save state in LocalStack. They are:• Persistence• State Export & Import• Cloud Pods ## Documentation• State management: https://docs.localstack.cloud/user-guide/state-management/ • Cloud Pods: https://docs.localstack.cloud/user-guide/state-management/cloud-pods/ • Persistence: https://docs.localstack.cloud/user-guide/state-management/persistence/ • State Export & Import: https://docs.localstack.cloud/user-guide/state-management/export-import-state/