Skip to main content

How We Built a Cloud Platform Using Netflix OSS

Carl Quinn (Riot Games)
Cloud
F150
Average rating: ****.
(4.75, 8 ratings)
Slides:   1-ZIP 

This talk will describe the libraries, services and tools from the Netflix OSS stack that we used, our adaptations and extensions, and how we put them together with a nifty Java library stack to form a cohesive platform.

On the Java development side, we created a robust ReST client/server stack, then added in some of the Netflix OSS libraries to build a simple library kit for quick development of robust, cloud-ready Java services. We even have permutations of it bundled into Dropwizard for fast and easy development.

On the build side, we adopted Aminator’s pre-baked image model, but extended Aminator to use Chef to leverage our existing cookbook library.

At deployment time, we use Asgard as our general cloud portal, but have extended it with a richer user-data generation mechanism to allow for richer deploy-time metadata injection. Then at launch, instead of using Chef for bootstrapping and configuration, we use an extended Eureka system for service discovery and an built an Archaius backend service for dynamic configuration.

And, last but not least, we use Edda and the Simian Army for security and conformance auditing, as well as routine cleanup tasks, and Ice for account usage and billing reports.

Photo of Carl Quinn

Carl Quinn

Riot Games

Carl Quinn has been developing software professionally for 34 years, starting with BASIC on an Apple II, slogging through C/C++ on DOS, Windows and embedded, and finally landing in the Java-on-Linux world. The one thread through his career has been an inexplicable attraction to developer tools, spending time building them at Borland (C++ & Java IDEs), Sun (Java RAD), Google (Java & C++ build system), Netflix (Java build and cloud deployment automation) and most recently at Riot Games (Cloud Architect). Carl also co-hosts the Java Posse podcast, the #1 ranked Java technology podcast.