GoodData: The DevOps Story @ FIT CVUT October 16 2013

transcript

GoodData:The DevOps StoryJaroslav GergicVP, RD & Operations

FIT CVUT / MI-AIT (Případové studie aplikace a řízení IT) / Oct 16 2013

OPEN CLOUD BI PLATFORM

WHY GOODDATA

73,000 Satisfied Users

99.5% Uptime SLA

84.7%Adoption

20B Rows Under Management

50+PoweredBy Partners

1,000,000 data integrations per week

28kUsers at one customer

Security Certified

20,000Data Warehouses Under Management

1Delightful Interface

OUR CUSTOMERS

UNLOCK DATA

UNITE DATA

MONETIZE DATA

THE GOODDATADEVOPSSTORY

▸ traditional structure - functional separation▸ handovers between teams▸ QA is there to protect OPERATIONS▸ ~20 people in R&D, QA and Operations

GoodData back in 2008...

FRONTENDENGINEERING

BACKENDENGINEERING

OPERATIONS

▸ Which one is more suitable for SaaS?

Alternatives

ENGINEERING

OPERATIONS

ENGINEERING

OPERATIONS

▸ functional specialization▸ consistency▸ economies of scale▸ flexibility to reallocate resources within department

Traditional structure - PROSENGINEERING

OPERATIONS

▸ lack of ownership▸ throwing stuff over the wall▸ tendency to blame culture

▸ delays caused by handovers▸ tendency to create bottlenecks while scaling

Traditional structure - CONSENGINEERING

OPERATIONS

▸ ~55 people in total at the time▸ still keeping the traditional structure▸ starting to feel the pain▸ DevOps to the rescue!

GoodData back in 2011...

UI CPS

OPERATIONS

APP ROLAP AMS

WHAT ISDEVOPS?

▶ Beware: The code you write can wake you up in the middle of the night! (Literally speaking.)

DevOps in a SaaS Company

▶ What is DevOps?○ integrated cross-functional teams○ Development + QA + Operations

▶ OK, so What do DevOps do?○ It is not only about developing software, it is also about

running it on behalf of your customers:■ monitoring, error reporting & alerting■ ongoing performance optimizations & fine tuning■ incremental feature rollouts (risk mitigation)

▶ All the above influences the way we architect and develop our software and technologies we use.

▸ sense of ownership▸ alignment of priorities

▸ all functions part of one team▸ bigger autonomy

▸ can do releases on team level▸ no handovers (throwing stuff over the wall)

▸ leading to shorter cycle times

DevOps - PROSENGINEERS

▸ limited functional separation▸ assuming small agile teams▸ harder to recruit people with wide range set of skills

▸ limited flexibility▸ harder changes beyond and above team level

▸ security▸ more people with production access keys

DevOps - CONSENGINEERS

▸ bringing DevOps to the next level▸ adding technical product manager

▸ a.k.a. functional architect▸ a.k.a. product owner▸ also UI designer in some teams

▸ even tighter loop of the development process▸ removed handover between PM and R&D

DevOps++ ConceptPM+

ENGINEERS+

▸ ~90 people in about ~12 teams▸ most of them using DevOps++ model

▸ each team owns subset of production servers▸ a sub-cluster in GoodData terminology

▸ 1 major release each month▸ coordinated across all teams

▸ while delivering ~60% of features independently▸ in zero-downtime releases twice a week

GoodData DevOps in 2013

Thank you!

GoodData: The DevOps Story @ FIT CVUT October 16 2013

Technology