Getting started on AWS is easy, but building a scalable, reliable, and performant product in the cloud can be a challenge for startups and enterprises alike. Netflix has famously migrated all our services to the cloud. Along the way, we have open-sourced large portions of our platform that helped make this a reality. In this talk, Mike McGarr (Manager – Netflix Developer Productivity) will provide a survey of the Netflix OSS products available. Mike will also share patterns and lessons Netflix learned migrating to the cloud. This talk will cover tools such as Nebula, Aminator and Spinnaker. Lastly, Mike will leave you with a roadmap for how to get started with Netflix OSS on your cloud today.

1. BUILD AND DEPLOY
TO THE CLOUD USING
NETFLIX OSS
Mike McGarr
Netflix Developer Productivity
@SonOfGarr
MikeMcGarr.com

5. Netflix streaming service started in 2007

6. migrate to the cloud

10. BUILD AND DEPLOY TO THE CLOUD USING
MIKE MCGARR
@SONOFGARR
MIKEMCGARR.COM

12. ▸ create an installable Java microservice
▸ install and bake a microservice
▸ define our AWS deployment
▸ create a deployment pipeline

14. ▸ create an installable Java microservice
▸ install and bake a microservice
▸ define our AWS deployment
▸ construct a deployment pipeline

15. A SIMPLE MICROSERVICE
▸ Groovy
▸ Spring Boot

20. Gradle's Application Plugin gives us a
runnable app

22. Immutable server pattern

24. NEBULA PLUGINS
dependency lock plugin
resolution rules plugin
dependency recommender plugin
lint plugin
metrics plugin
test plugin
publishing plugin
ospackage plugin
http://nebula-plugins.github.io

29. Nebula's ospackage plugin
produces a Debian package

30. ▸ create an installable Java microservice
▸ install and bake a microservice
▸ define our AWS deployment
▸ construct a deployment pipeline

31. unit of deployment

32. BAKING

36. sudo aminate /
-e ec2_aptitude_linux /
-b ubuntu-base-ami-ebs /
helloworld_1.0.0_all.deb

38. ▸ create an installable Java microservice
▸ install and bake a microservice
▸ define our AWS deployment
▸ construct a deployment pipeline

40. JUST LAUNCH AN
INSTANCE, RIGHT?

41. EACH INSTANCE NEEDS
▸ Amazon Machine Image (AMI)
▸ security groups
▸ launch configurations
▸ elastic load balancers
▸ auto-scaling groups

43. SPINNAKER
▸ Cloud infrastructure management
▸ Deployment pipelines
▸ microservice architecture
▸ Java & Groovy Spring Boot microservices

44. SPINNAKER COMMUNITY AMI

49. ▸ create an installable Java microservice
▸ install and bake a microservice
▸ define our AWS deployment
▸ construct a deployment pipeline

50. Continuous delivery

52. BASTION, JENKINS & SPINNAKER

53. JENKINS BUILD JOB
▸ checkout from Github
▸ ./gradlew clean build
buildDeb
▸ publish debian package

62. WHERE TO NEXT?
▸ Edda (track cloud changes)
▸ Eureka (service discovery)
▸ Chaos Monkey (kill prod instances)
▸ Atlas (large scale metrics)

63. TAKEAWAYS

64. MAKE APPLICATIONS
EASY TO INSTALL

65. MAKE SERVERS
IMMUTABLE

66. THE CLOUD IS
HARD

67. QUESTIONS?MIKE MCGARR
@SONOFGARR
MIKEMCGARR.COM