In database architecture, the query processing involves an intermediate layer called DB proxy, which acts as a query engine to parse and route queries to different databases based on shard keys. A service called topology manages the physical and logical topology of the databases, including shard keys and tables. Using read replicas for load sharing ensures high availability and reliability by serving reads even if a primary database goes down. While the complex setup may initially impact performance, solutions like query caching in memory help optimize query parsing for efficient processing.
Sammy Steele is a Senior Staff Engineer at Figma, and the tech lead for their databases team. She previously worked at Dropbox, where she built out their petabyte-scale metadata storage and search systems.
Sammy recently published a blog called “How Figma’s databases team lived to tell the scale”. The blog went viral and made it to the top of Hacker News. We invited Sammy on the podcast to learn more, and she is our guest today.
Check out Figma Config at https://config.figma.com/.
Sean’s been an academic, startup founder, and Googler. He has published works covering a wide range of topics from information visualization to quantum computing. Currently, Sean is Head of Marketing and Developer Relations at Skyflow and host of the podcast Partially Redacted, a podcast about privacy and security engineering. You can connect with Sean on Twitter @seanfalconer .
The post Database Scaling at Figma with Sammy Steele appeared first on Software Engineering Daily.