Upload
devops-israel
View
489
Download
1
Embed Size (px)
DESCRIPTION
Not so long ago Kenshoo had a very simple system. A server and a database. When they needed to scale the system to support more customers they simply created a new pair of servers. This was very easy to operate and manage in production. The release process was very simple in this "shared-nothing" architecture since there were hardly any dependencies. Test and deployment automation was easy as well. Over time, silos between Dev/QA/IT/Ops formed. Each with their own independent tools and methodologies. But what happens when this architecture failed to meet the scale demands? The system needed to be broken into pieces, each with it's own domain of responsibilities. Suddenly there were tens of different services in production, each with its own dependencies, release cycle, technologies. How do teams adjust? What dev / test / release / ops processes need to change? What about tools? Tal will cover these and more in this talk. Speaker: Tal Salmona, Kenshoo Tal serves as a chief architect at Kenshoo and leads the plaforms group. Prior to that Tal led the Spring Insight project at VMware, worked at HP and founded a startup that dealt with social media analytics. He grows vegetables in his garden and enjoy riding his mountain bikes
Citation preview
Team RefactoringTal Salmona
Chief Architect, Kenshoo
Change
Comple
xity
It’s not about tools
Delivery
Photo by tableatny
“Make sure you restart this other service before upgrading mine
“Follow these 20 simple steps in the wiki to install the service
“Make sure you create a queue before running the service
“Let me know if it worked
Developer to IT
IT to Developers“BTW, we’re upgrading to MySQL 5.6 tomorrow in production
“The upgrade scripts are backed up on the NAS server
“I can do this with one line of perl
Responsibility
Photo by Usman Sheikh
Shift of responsibility
Vertical or horizontal?
Can there be clear boundaries?
Role of QA
Should IT be part of a feature team?
What works for us
Service interface
Simulate production as much as possible
Put everything in Git
Talk
All tech under one roof
Thanks
היהפוך כושי עורו, ונמר חברבורותיוירמיהו כ”ג
היקנפג מפתח את לינוקסו, ואיש סיסטם יקמט את סקריפטו README.md line 5