Slide 1

Slide 1 text

WORKING WITH YOUR DBA IN A DEVOPS WORLD @DBSMASHER

Slide 2

Slide 2 text

@dbsmasher @DBSMASHER…AKA SILVIA BOTROS ▸ Principal DBA @ SendGrid ▸ Nearly 6 years ▸ Accidentally a DBA

Slide 3

Slide 3 text

@dbsmasher SENDGRID ▸ 55,000+ paying customers in 100+ countries ▸ 1 trillion emails processed ▸ > 50% of the world’s email addresses receive emails through SendGrid ▸ Within the last 12 months

Slide 4

Slide 4 text

@dbsmasher DEVOPS! “Unifying the operations and engineering teams under one umbrella” — Wikipedia

Slide 5

Slide 5 text

@dbsmasher NEW BIG PRODUCT FEATURE….A STORY ‣ Product asks for feature ‣ Make stories ‣ Assign points ‣ Write some code ‣ Test in … some environment ‣ Deploy ‣ Profit?? ‣ …..hold up

Slide 6

Slide 6 text

@dbsmasher YES..THERE IS A TWIST TO THIS HAPPY STORY

Slide 7

Slide 7 text

@dbsmasher "LET’S HIRE A DBA”

Slide 8

Slide 8 text

@dbsmasher

Slide 9

Slide 9 text

@dbsmasher

Slide 10

Slide 10 text

@dbsmasher “BUT WE TESTED!” ‣ How many users were in your test? ‣ How much variation in load did you test? ‣ Do you know your peak achievable load? ‣ Did you test your assumptions about the database? ‣ Are you afraid of this new product succeeding?

Slide 11

Slide 11 text

@dbsmasher

Slide 12

Slide 12 text

@dbsmasher

Slide 13

Slide 13 text

@dbsmasher HERE ARE STEPS YOU CAN TAKE

Slide 14

Slide 14 text

@dbsmasher TECHNOLOGY CATALOG Know *why* you are using a given tool ‘Boring’ doesn’t have to mean not challenging credit: Coda Hale

Slide 15

Slide 15 text

@dbsmasher

Slide 16

Slide 16 text

@dbsmasher THINGS TO CONSIDER ▸ Are you already multi datacenter/multi AZ? ▸ What kind of data is going into this new thing? ▸ Draw a line between that data and your monthly invoices ▸ Can you *really* not use something already in your stack for this?

Slide 17

Slide 17 text

@dbsmasher “A complex System that works is invariably found to have evolved from a simple system that worked. ” — John Gall

Slide 18

Slide 18 text

@dbsmasher WRITE THINGS DOWN Know your stakeholders Spoiler: it is NOT just product or even just the customers Ops? InfoSec? Finance? ETL?

Slide 19

Slide 19 text

@dbsmasher “The rule is, in the absence of information, humans will fill up the vacuum” — Rands

Slide 20

Slide 20 text

@dbsmasher ARCHITECTURE REVIEW. IT’S A GOOD THING ▸ Who needs to be there? ▸ Those building the thing ▸ Those looking to learn ▸ Those who care ▸ This is NOT a technical smackdown

Slide 21

Slide 21 text

@dbsmasher COLLECTIVE EXPERIENCE IS AN ASSET

Slide 22

Slide 22 text

@dbsmasher

Slide 23

Slide 23 text

@dbsmasher FIRE DRILLS A cross functional exercise Documented Published internally

Slide 24

Slide 24 text

@dbsmasher TECH DEBT

Slide 25

Slide 25 text

@dbsmasher TECH DEBT IS NOT JUST IN CODE ▸ Databases are the ultimate rug to your tech debt fairy dust ▸ Success breeds tech debt in your data-stores ▸ Only so much adding an index can do ▸ Changing the wheels at 100 mph

Slide 26

Slide 26 text

@dbsmasher BUT….CLOUD!

Slide 27

Slide 27 text

@dbsmasher PRODUCT MANAGERS HAVE A ROLE OUTSIDE NEW THINGS A product manager informed about your tech debt is an asset Be honest to the business about incurred tech debt

Slide 28

Slide 28 text

@dbsmasher REMEMBER… Stability is a feature; And it better be one before customers flock out Stability is a full company effort

Slide 29

Slide 29 text

@dbsmasher FINALLY, YOU DON’T NEED TO HIRE A DBA TO DO ALL THIS

Slide 30

Slide 30 text

@dbsmasher @dbsmasher [email protected]