SlideShare a Scribd company logo

Devopstools

•
•
Ariel Moskovich
Ariel Moskovich

This document discusses the evolution of DevOps tools at AppsFlyer and provides examples. It notes that AppsFlyer processes around 4.9 billion events per day across 120 services running on elastic infrastructure with dozens of daily deployments and a team of 25 developers. The one team philosophy motivates building internal tools to meet operational needs, extend existing tools, learn new technologies, and improve collaboration between development and operations. Considerations for new tools include needs, usability, audience, maintenance, and time constraints. Examples given are a mapping tool called Sniffer, aggregated monitoring reports from Sensu, and an authentication system called Bouncer.

Related slideshows

How do you agile your global team to contribute to openstack
How do you agile your global team to contribute to openstackHow do you agile your global team to contribute to openstack
How do you agile your global team to contribute to openstack
 
CUHK CSCI 4140 2015 Spring Guest Lecture - Agile Development
CUHK CSCI 4140 2015 Spring Guest Lecture - Agile DevelopmentCUHK CSCI 4140 2015 Spring Guest Lecture - Agile Development
CUHK CSCI 4140 2015 Spring Guest Lecture - Agile Development
 
Career_Model
Career_ModelCareer_Model
Career_Model
 
1 of 14
Download to read offline
DevOps Tools Evolution
Today's Menu ● AppsFlyer in numbers ● Rnd structure in AppsFlyer ● Our DevOps philosophy ● Motivation for creating DevOps tools ● Setting requirements and project assignment ● Example for tools we built internally ● Live demo and the developer angle
Devopstools
AppsFlyer in numbers ● ~ 4.9 billions events per day ● ~ 120 services ● Elastic hundreds to 1K instances ● Dozens of deployments per day ● 25 people in development ● 1 team
One team philosophy
That's me
Devopstools
Devopstools
Motivations ● Actual operational needs ● Extend existing tools ● Learn new technologies ● Familiarize the production environment for new Rnd members ● Blur the line between Dev and Ops ● Improve the bonding inside the team
Considerations ● Needs, why do we need this project? ● Usability – How do I see myself using the project? ● The target audience. ● The developer's background (Front, Mobile, etc) ● Will the developer be better familiar with production environment? ● How are we going to maintain the project? ● What are the time constraints? ● Can we roll it out in stages? ● Can we release it outside?
Today's Examples ● Sniffer: Mapping tool (Artyom Shein) ● Sensu Reports: Aggregated reports of Sensu (Avner Schwartz) ● Bouncer: Authentication and Authorization (Reshef Mann)
Live Demo
And... Rock n Roll
Questions?

More Related Content

Devopstools

  • 2. Today's Menu ● AppsFlyer in numbers ● Rnd structure in AppsFlyer ● Our DevOps philosophy ● Motivation for creating DevOps tools ● Setting requirements and project assignment ● Example for tools we built internally ● Live demo and the developer angle
  • 4. AppsFlyer in numbers ● ~ 4.9 billions events per day ● ~ 120 services ● Elastic hundreds to 1K instances ● Dozens of deployments per day ● 25 people in development ● 1 team
  • 9. Motivations ● Actual operational needs ● Extend existing tools ● Learn new technologies ● Familiarize the production environment for new Rnd members ● Blur the line between Dev and Ops ● Improve the bonding inside the team
  • 10. Considerations ● Needs, why do we need this project? ● Usability – How do I see myself using the project? ● The target audience. ● The developer's background (Front, Mobile, etc) ● Will the developer be better familiar with production environment? ● How are we going to maintain the project? ● What are the time constraints? ● Can we roll it out in stages? ● Can we release it outside?
  • 11. Today's Examples ● Sniffer: Mapping tool (Artyom Shein) ● Sensu Reports: Aggregated reports of Sensu (Avner Schwartz) ● Bouncer: Authentication and Authorization (Reshef Mann)