MLB's technology transformation aimed to modernize their stack and build a dynamic API capable of fetching data dynamically from various sources. The resulting REST-based Stats API was successful but led to complexity and payload size issues. To address these challenges, MLB recognized the need for a more scalable and performant API architecture, which led them to adopt GraphQL. By exposing all features of their StatsAPI via a new GraphQL subgraph, they were able to streamline data orchestration and provide uniform representation of game-related queries across multiple consumer-facing products. The adoption of GraphQL enabled MLB to deliver personalized experiences without overburdening client-side logic, and its centralized approach prevented inconsistent data contracts and reduced complexities.