It probably won’t come as a surprise that given the amount of traffic, we wanted to built out a robust monitoring and alerting solution. Of course given such load, a lot of the requested data was heavily cached at various levels, including the CDN, the API infrastructure’s caching layer, and other mechanisms. However given the United States’ outsized influence on global matters, US elections are of significant interest around the world as evidenced by this image which breaks down Decision Desk HQ DNS queries by data center:Īs mentioned, during this three day period almost 3 billion requests and 4 terabytes of data were processed: There’s a saying in US politics, “ all politics is local“. For instance here is a screenshot of the Pennsylvania coverage breakdown: All Politics is Local, But Interest is Global For instance the following embed screenshot was taken from Vox’ live election results page:ĭecision Desk HQ also publishes a public set of interactive infographics at which not only breaks down national results but also state results. Others take advantage of “embeds”, which are slick infographics produced by Decision Desk HQ and which can be, well, embedded into client websites. Some query the API directly, retrieving information about the status of the presidential election, specific congressional races, or even the status of all races occurring within a specific state. These clients used the data in a variety of ways. Data in Multiple Formatsĭecision Desk HQ clients include numerous media outlets such as Vox, Business Insider, and The Economist. In this post I’ll summarize the different ways in which the APIs were used, the amount of data processed, and how API infrastructure was monitored to ensure smooth operation throughout the election.
Our infrastructure provided API services which assisted in the processing of nearly 3 billion requests and 4 terabytes of data over a 72 hour period beginning with the start of election reporting at 6pm Eastern on November 3rd. We’re excited to announce DreamFactory’s role in Decision Desk HQ’s election reporting operations. This feat was accomplished in part because of Decision Desk HQ’s forward-thinking views on technology allows them to gather, process, and distribute election results in a very performant and efficient manner.
#Decision desk hq full
Decision Desk HQ’s status as an election reporting juggernaut grew dramatically in the recent US election due to their calling the presidential election for Joe Biden a full 48 hours before competing operations across the media and major television networks. Founded in 2012 with the goal of improving the speed in which US election data is reported and in which elections are called, the staff has since grown from its founder to hundreds of employees and volunteers located around the United States.
Yet our most interesting project to date didn’t involve a member of the Fortune 100 rather, the client is a relative upstart named Decision Desk HQ. As you might imagine, big companies means big API problems. Among others we’re presently working with one of the world’s largest auto manufacturers, one of the world’s largest pharmaceutical companies, one of the world’s largest consulting companies, and one of the world’s largest computer hardware manufacturers. To put this into perspective, although our client base ranges widely in terms of both industry and company size, we often work with organizations tending towards the larger end of the scale. Many of these projects involve integrating the DreamFactory platform into a much larger technology ecosystem. Over the years the DreamFactory team has collaborated on a lot of really interesting API-oriented projects.
0 kommentar(er)
