{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"GraphQL Radio","title":"One Edge Provider - Build In Public With The Stellate Team Behind OEP","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/b113687b\"></iframe>","width":"100%","height":180,"duration":2251,"description":"Show Notes:\nIn this episode of GraphQL Radio, Andreas Heiberg, Stellate's Engineering Manager, guides a discussion with colleagues on the deployment of One Edge Provider (OEP). A transformative project for Stellate's system, aimed at significantly enhancing Stellate's caching services. Ensuring 2x faster GraphQL Edge Caching.\nThe team, consisting of project lead Dominik Petrick, Thomas Heyenbrock, and Stephan Schneider, reflects on challenges, lessons learned, critical decisions, and the transition to a more scalable architecture. This episode delves into Stellate's evolution, explores the motivation behind OEP, and highlights pivotal moments in decision-making; illustrating Stellate's steadfast commitment to innovation.\nTopics Discussed:\nIntroduction to One Edge Provider (OEP)\nOrigins of Stellate and GraphCDN\nDeployment Strategies\nDecision to Change the System\nScalable and Unified Architecture\nEnd-To-End Testing\nInitial Limitations\nChallenges\nChoosing Rust and Fastly\nInitiating the OEP Project\nOEP Deployment Complexities\nRollout Challenges and Lessons Learned\nTraffic Replay System\nBuilding Confidence\nRust and TypeScript Nuances\nRust's Performance\n\nLinks:\nStellate\nAndreas Heiberg\nDominic Petrick\nStephan Schneider\nThomas Heyenbrock","thumbnail_url":"https://img.transistorcdn.com/rxHE9b5nr83pIVgwSFGWYNdyqPcyFQb0y9W2Igjm-tw/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzI5MzQ2LzE2NjE3/NjA3MzQtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}