Team Refactoring
Tal Salmona
Chief Architect, Kenshoo
Change
ple

Com

xity
It’s not about tools
Delivery

Photo by tableatny
Developer to IT
“Make sure you restart this other service before upgrading mine
“Follow these 20 simple steps in the wiki ...
IT to Developers
“BTW, we’re upgrading to MySQL 5.6 tomorrow in production
“The upgrade scripts are backed up on the NAS s...
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 t...
What works for us
Service interface
Simulate production as much as possible
Put everything in Git
Talk
All tech under one ...
‫‪Thanks‬‬
‫היהפוך כושי עורו, ונמר חברבורותיו‬
‫ירמיהו כ”ג‬
‫היקנפג מפתח את לינוקסו, ואיש סיסטם יקמט את סקריפטו‬
‫5 ‪READM...
DevOps Days Tel Aviv 2013: Team refactoring: How rearchitecting systems affects people, teams & processes - Tal Salmona
DevOps Days Tel Aviv 2013: Team refactoring: How rearchitecting systems affects people, teams & processes - Tal Salmona
DevOps Days Tel Aviv 2013: Team refactoring: How rearchitecting systems affects people, teams & processes - Tal Salmona
Upcoming SlideShare
Loading in …5
×

DevOps Days Tel Aviv 2013: Team refactoring: How rearchitecting systems affects people, teams & processes - Tal Salmona

531 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
531
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

DevOps Days Tel Aviv 2013: Team refactoring: How rearchitecting systems affects people, teams & processes - Tal Salmona

  1. 1. Team Refactoring Tal Salmona Chief Architect, Kenshoo
  2. 2. Change
  3. 3. ple Com xity
  4. 4. It’s not about tools
  5. 5. Delivery Photo by tableatny
  6. 6. Developer to IT “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
  7. 7. 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
  8. 8. Responsibility Photo by Usman Sheikh
  9. 9. Shift of responsibility Vertical or horizontal? Can there be clear boundaries? Role of QA Should IT be part of a feature team?
  10. 10. What works for us Service interface Simulate production as much as possible Put everything in Git Talk All tech under one roof
  11. 11. ‫‪Thanks‬‬ ‫היהפוך כושי עורו, ונמר חברבורותיו‬ ‫ירמיהו כ”ג‬ ‫היקנפג מפתח את לינוקסו, ואיש סיסטם יקמט את סקריפטו‬ ‫5 ‪README.md line‬‬

×