Contenu connexe Similaire à Envato Dev Ops - Alt.Net Melbourne (20) Envato Dev Ops - Alt.Net Melbourne1. Dev Ops, Ruby, Rails,
and Envato
A team of 8 deploy heaps of times a day to a Ruby on
Rails app that has scaled up to around 20 million
requests a week without an ops team.
lolwut?
Thursday, 30 June 2011
2. John Barton
@johnbarton
john@envato.com
Thursday, 30 June 2011
3. Envato?
http://envato.com
Thursday, 30 June 2011
13. Rails 0.13b
No Users
No Traffic
Thursday, 30 June 2011
16. ActiveDen (nee FlashDen)
AudioJungle
ThemeForest
VideoHive
GraphicRiver
CodeCanyon
3D Ocean
Tuts+ Marketplace
PhotoDune
Thursday, 30 June 2011
17. Rails 2.3.11
830,462 Users
22 Million Requests Weekly
Thursday, 30 June 2011
21. What do you need to do
the same?
Thursday, 30 June 2011
22. Some technical
infrastructure, some
business/cultural
Thursday, 30 June 2011
25. “Culture of respect &
trust, good attitude toward
failure...”
Ted Dzubia
Thursday, 30 June 2011
26. “How about "culture of
stop fucking up"?”
Ted Dzubia
http://teddziuba.com/2011/03/devops-scam.html
Thursday, 30 June 2011
27. A problem of competing
priorities
Thursday, 30 June 2011
29. Outsource commodity
platform bits:
virtualisation/cloud, have
rackspace take care of db/
mailserver
Thursday, 30 June 2011
30. Ensure the dev team has
the skills to take care of the
rest
Thursday, 30 June 2011
31. Take advantage of an
individual's talents, but
don’t rely upon them
ie. don’t accidentally create an ops guy
Thursday, 30 June 2011
32. OK to have specialists... for
special work.
Keeping the app running
isn’t “special”
Thursday, 30 June 2011
36. 3 Developers
30 minute feedback cycle
deploy, discuss on forums,
deploy again
Thursday, 30 June 2011
39. We’ve all been doing dev
long enough to see this
stuff screwed up over and
over again
Thursday, 30 June 2011
40. Decision 3:
Don’t do all that stuff
Thursday, 30 June 2011
42. "The fault, dear
Brutus, is not in our
QA or Ops,
But in ourselves."
Thursday, 30 June 2011
45. Both as a team and as
individuals we own our
work from when we are
asked to do it...
Thursday, 30 June 2011
46. ... until is is demonstrably
error free and performant
in production
Thursday, 30 June 2011
51. LEAN / TPS Principles
...without the process
Thursday, 30 June 2011
53. You cannot write code any
faster than you can deploy
it to production
Thursday, 30 June 2011
55. A. B. C.
Always Be Cmerging
(the c is silent)
Thursday, 30 June 2011
56. I would not want to try this
with Subversion, or Visual
Source Safe... and I never
had enough money to try
“Team Foundation Server”
Thursday, 30 June 2011
57. Use GIT
http://git-scm.com/
Thursday, 30 June 2011
58. Dark Launch
Feature Flags
Private Beta
Thursday, 30 June 2011
60. We do trip up running this
fast
Thursday, 30 June 2011
61. But through years of
openness with our users
via our forums and owning
up to our mistakes
Thursday, 30 June 2011
62. ... we’ve ended up with a
(relatively) sympathetic
community
Thursday, 30 June 2011
64. Traffic peaks during US day
means that if things go
wrong we’re usually asleep
Thursday, 30 June 2011
65. But it makes it very easy to
deploy during our business
hours
Thursday, 30 June 2011
67. No point you solving the
same problem as the guy
down the street
Thursday, 30 June 2011
68. No point the guy down the
street solving the same
problem you did last week
Thursday, 30 June 2011
74. You can't
trust “the
cloud” but
you can
trust “the
cloud to
be “the
cloud”.
Thursday, 30 June 2011
75. Make a conservative
platform choice so we
don’t have to sweat the
details
ie. Ubuntu 10.4 LTS
Thursday, 30 June 2011
76. I guess you guys have to
choose like Windows
Ultimate 2009 Edition?
Thursday, 30 June 2011
77. Seriously though, Ruby guys
love shiny new things, and
we’re spoiled for choice
_even_ when it harms us.
Thursday, 30 June 2011
78. So we make an effort to
keep the stack as Vanilla as
possible
Thursday, 30 June 2011
81. Babushka
http://babushka.me/
Thursday, 30 June 2011
86. Use Dollhouse
https://github.com/geelen/
dollhouse
To drive babushka remotely
Thursday, 30 June 2011
88. A lot of people I take
seriously, take Chef
seriously.
http://wiki.opscode.com/
Thursday, 30 June 2011
90. Capistrano
https://github.com/
capistrano/capistrano
Thursday, 30 June 2011
94. I’m so used to having it I
can’t even remember how I
ever deployed database
changes in the past
Thursday, 30 June 2011
96. Not as big a deal as
everyone thinks
Thursday, 30 June 2011
97. .NET runtime is faster... but
it’s really not that big a deal
Thursday, 30 June 2011
98. Shared-nothing load
balanced app servers + out
of request queue workers
not rocket surgery
Thursday, 30 June 2011
100. There is no code faster
than no code.
Thursday, 30 June 2011
101. Why I’m happier than I was
as a .NET programmer
Thursday, 30 June 2011
103. No Viewstate
(Yes I heard you’ve got
MVC now instead)
Thursday, 30 June 2011
104. A culture of people who fix
things instead of waiting for
them to be fixed
Thursday, 30 June 2011
105. People who care about
expressiveness of code and
finding the right
abstractions
Thursday, 30 June 2011