destroy the wall between development and it ops teams

17

Click here to load reader

Upload: panagiotis-moustafellos

Post on 16-Apr-2017

1.076 views

Category:

Engineering


2 download

TRANSCRIPT

Page 1: Destroy the wall between development and it ops teams

Destroy the wall betweenDevelopment and IT Ops teamsBuild and ship better software that scales

28 Nov 2015

Panagiotis MoustafellosLead DevOps, PeoplePerHour

Page 2: Destroy the wall between development and it ops teams

What is DevOps

DevOps (short for Development & Operations) is an agile methodology in softwaredevelopment and release.

DevOps is a culture applied to organisations aiming to bridge the gap between Devand Ops.

Page 3: Destroy the wall between development and it ops teams

DevOps: The drivers

Stakeholders' demand to reduce Time-to-Market

Use of agile development methodologies

Virtualized & Cloud environments

Availability of SaaS and PaaS that do the heavy lifting

Vibrant Ecosystem in Distributed, HA/FT systems

Robust Configuration Management, Automation & Monitoring toolkits

DevOps integration targets product delivery, QA & RAD targetting faster developmentand deployment cycles

Page 4: Destroy the wall between development and it ops teams

Silos: The Dev and IT Ops silos

Development team "waiting"

Operation team "standing by"

Product team "pushing"

Page 5: Destroy the wall between development and it ops teams

DevOps: An Un-Blocker

Communication

Shared goals

Shared responsibility

A wider domain expertise OODA loop

Page 6: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case

PeoplePerHour is one of the largest Freelancer Marketplaces

Over a million active users

Targets SMEs

Enables hiring talent using a pool of expert freelancers

Enables remote work

Page 7: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case; teams

Development

Product

Marketing & Community building

Customer Support

Payments & Fraud

Data Science & Business Intelligence

DevOps

Page 8: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case; before

Before adopting DevOps:

Tests were not maintained properly

Builds would ship untested

Development / Staging / Production environments not identical

Huge monolithic app

Systems/Ops a black box

Scaling needed planning and manual intervention

Metrics lacking

Page 9: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case; after

After adopting DevOps:

Tests run per Pull Request, per Build

Fully automated CI / CD pipeline

Infrastructure as Code

Development / Staging / Production environments are identical

Switching to a microservices oriented architecture, ready for scale. Following the12-factor app paradigm as close as we can

Proper central log aggregation and analysis

Page 10: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case; mission

Made big wins, now to make more profit:

Re-use our shiny SOA to bootstrap new products faster

Make DevOps team obsolete and replace it in favor of DevOps-as-a-culture

Create joined teams cross-organisation to tackle trivial problems

Make our former DevOps team a combat-mission team

Page 11: Destroy the wall between development and it ops teams

DevOps: The PeoplePerHour case; Community

We joined forces with other startups to create a DevOps community in Athens.

Reach out to my team, we'd love to share stories and help eachother out in DevOpstransformation.

Page 12: Destroy the wall between development and it ops teams

DevOps: Words of advise

To junior developers: If you can afford to: choose Tech, Workflows and Team oversalary. It will pay out in a couple of years. That doesn't mean low-balling yourself orlet bosses/seniors take advantage of you.

To senior developers: Combine techical ability with domain experience. Lift yourteam to your level. Speak up. Don't be a hero programmer. Get payed for the valueyou bring in. Embrace change.

To VPs and C-levels: Hire people smarter than you. Bet in teams and not in Heros.Let your engineers run the product as well; they know it, they've built it. UseDevOps

Page 13: Destroy the wall between development and it ops teams

Creating a community; Why Athens DevOps?

Scene is young and vibrant

Rapidly evolving ecosystem

Organisations are interested in using DevOps

Tales of success (and failure) creates collective domain experience

Group goal:

Build a community of professionals practicing DevOps, pushing forward bestpractices

Page 14: Destroy the wall between development and it ops teams

Some Group topics

Infrastructure Architecture and Systems Automation

Configuration Management tools

Logging Analysis and Metrics Visualization

Scalability, High Performance, High Availability / Fault Tolerance

IaaS / PaaS

Continuous Integration / Continuous Delivery

Dev and Ops group dynamics

the list goes on...

Page 15: Destroy the wall between development and it ops teams

Getting involved

Spread the word, stay engaged

Meetup group https://meetup.com/Athens-DevOps/

Slack (#athens at http://devopsengineers.com)

LinkedIn, Facebook groups

Twitter - #AthensDevOps

Page 16: Destroy the wall between development and it ops teams

Thank you

28 Nov 2015

Panagiotis MoustafellosLead DevOps, [email protected] (https://mail.google.com/mail/?view=cm&fs=1&tf=1&[email protected])

https://gr.linkedin.com/in/pmoust (https://gr.linkedin.com/in/pmoust)

@pmoust (http://twitter.com/pmoust)

Page 17: Destroy the wall between development and it ops teams