devops, what should you decide, when, why & how - vinita rathi

14
VINITA RATHI Co Founder | Systango Ex VP | Goldman Sachs DevOps, What should you decide, when, why & how?

Upload: jaxlondonconference

Post on 12-Apr-2017

151 views

Category:

Software


0 download

TRANSCRIPT

Page 1: DevOps, what should you decide, when, why & how - Vinita Rathi

VINITA RATHICo Founder | SystangoEx VP | Goldman Sachs

DevOps, What should you decide, when, why & how?

Page 2: DevOps, what should you decide, when, why & how - Vinita Rathi

• My limited experience in back office and post trade space • I left Goldman in late 2012• My understanding of DevOps

Disclaimers

www.Systango.com

Page 3: DevOps, what should you decide, when, why & how - Vinita Rathi

DevOps in nutshell

• Objective • Emphasis on performance and quality• Feedback process• Continuous development

www.Systango.com

Page 4: DevOps, what should you decide, when, why & how - Vinita Rathi

My 5 Years at Goldman

• Pre Sales – decisioning via data and its patterns • Priorities – Stability, data sanity, operability with other services

vs Speed to deliver • Plan ahead - It took us 4 months to get needed servers • Business Knowledge - We had to do end to end testing

including data verification • Technology challenges• Use of `Blessed` Technologies • DIY

www.Systango.com

Page 5: DevOps, what should you decide, when, why & how - Vinita Rathi

Technology

• Client/Server Architecture • SOA, DF and RV• SVN, Maven, Gradle, Hudson, Atlassian JIRA, Sybase,

Autosys• Java, C#, Proprietary language• Windows • Train based deployment for services with 2 weeks cycle for

production deployment • On demand deployment for clients (based off a home grown

client framework)

www.Systango.com

Page 6: DevOps, what should you decide, when, why & how - Vinita Rathi

Ended up with ...

• Come up with a solution based on what you have got. • If you need X, request for X + 5.• Plan very well, and early. Cannot include last minute

user feedbacks. • Long decision making process. • Coherent and consistency throughout. • Matured technologies and developers.• Scalability and stability focused.

www.Systango.com

Page 7: DevOps, what should you decide, when, why & how - Vinita Rathi

Systango

• Small teams working on different projects • Varied Businesses• Cultural barriers • Limited Budget and resources• Time to market

www.Systango.com

Page 8: DevOps, what should you decide, when, why & how - Vinita Rathi

Technology

www.Systango.com

Page 9: DevOps, what should you decide, when, why & how - Vinita Rathi

Ended up with …

• Need to use Open source as much as possible • Need to keep up to date• Need to deploy and iterate fast

www.Systango.com

Page 10: DevOps, what should you decide, when, why & how - Vinita Rathi

DEVOPS LANDSCAPE 2015Made by HashiCorp

www.Systango.com

Page 11: DevOps, what should you decide, when, why & how - Vinita Rathi

How do you decide which tools to use at what layer?

The budget and scalability needs ? Do you have individuals working on infrastructure?Need build-time configuration or run-time?Richer feature set or Simplicity? Want to automate the infrastructure provisioning process?

www.Systango.com

Page 12: DevOps, what should you decide, when, why & how - Vinita Rathi

Bare Minimum

• Make deployments business-as usual.• Make everyone a performance engineer.• Strengthen the safety net with automated testing.• Be strict with version control.• Peer code review. • Implement end-to-end performance monitoring and metrics.

www.Systango.com

Page 13: DevOps, what should you decide, when, why & how - Vinita Rathi

Tools I love

• Nagios

• ELK

• Collectd

• Docker

• Monit

• Jenkins

• Ansible

www.Systango.com

Page 14: DevOps, what should you decide, when, why & how - Vinita Rathi

Thank You!

www.Systango.com