Seeing the World with Atlas

One of the biggest challenges of operating a global scale Content Delivery Network comes from understanding the network behaviors our end-users are experiencing. In order to help get a grasp on this, we’ve made use of Atlas, a measurement platform from the RIPE NCC. Here, we’ll talk a bit about the RIPE platform and how we use it to assess the behavior of the networks between our server and end-users. While it’s not the only way we use Atlas here at VDMS, it represents an area where the platform has had significant impact.

Continue Reading

Our 80/20

At Verizon Digital Media Services, we have the privilege of working on tools we’re proud of building.  But without a doubt, we are most proud of the team members who build them. We value our people, and create as many opportunities as possible for them to grow. At the core of this focus is our 80/20 program designed to harness growth potential. Many companies have programs they call “80/20”, where employees spend 80 percent of their time doing their main job, and 20 percent on passion projects. This is not that. We would like to share with you what and why DMS has created and adopted our own version of the 80/20.

Continue Reading

HTTP2 on the Edgecast CDN - Part 1

We are very excited to announce that HTTP/2 is available globally on the Edgecast CDN. Enabling HTTP/2 on a network as large as the Edgecast CDN was no small task. It required a tremendous amount of work across a number of teams. The endeavour of re-architecting our network to support HTTP/2 demanded such fundamental changes to our existing software stack that we want to share how and why we journeyed to where we are today.

Continue Reading

From Angular to Ember

Ember.js Tomster

In October 2015, the UI team at Verizon Digital Media Services started to reenvision the next generation of the Media Control Center, our customer facing CDN portal. The MCC was started in 2008 and is a traditional server-rendered application built on the .NET technology stack. Over the years, the front-end started playing a more prominent role using JavaScript technologies including jQuery, Angular 1, Gulp and CoffeeScript (popular at the time). Even though modern front-end tech was used, there were several pain points that frustrated front-end developers, leading the team to start thinking about how we wanted to build out MCC. Should we continue with Angular 1 and hope to switch to Angular 2 if there is an upgrade path, or should we switch to something else?

Continue Reading

Serializing to Parquet from Kafka with Exactly Once Guarantee

In the process of building our new analytics pipeline, we had to implement a typical lambda architecture. A lambda architecture is where you need to implement one massive process flow for real-time data and another for batch for the sake of performance. Mainly because the optimization points for real-time and batch are almost entirely unique to each other. Throughout our process of designing and improving the batch portion of our new lambda architecture, we faced many challenges and learned helpful lessons. We hope a summary of these takeaways will offer helpful insight to those implementing their own batch pipelines.

Continue Reading