How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017

Nov 16, 20171 like333 views

The document discusses how to continuously innovate with software given the rapid pace of new technologies being introduced and the large research and development budgets of corporations. It emphasizes the need to build solutions that address business needs rather than adopting every new tool, and to develop an adaptive culture within teams that can respond to changing technologies and industry trends. Examples are provided of how open source technologies like Docker have evolved and best practices for evaluating and using new software.

How to Survive
Continuous Innovation ?
Sebastien Goasguen

@sebgoa

How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017

Later raised $30M C round to “take on VMware”

Why this software ?
How do we ﬁnd them ?
How do we choose ?
Why do we adopt them ?

Trends or fashion ?
Euca, Openstack, CloudStack, Kubernetes, Lambda

Example:
“OMG Lambda is killing it, people are going
to skip containers and go straight to
serverless …and forget about your cloud…”

GAFA R&D ~ State Budget
2015 data, now ~$100B/y
France ~$70B
Israel ~$15B

Observations
• Perceived increased pace of software innovation

• R&D budgets of corporations is greater than state
(theoretical research)

• Not a “brain drain”, but a “corporate drain"

• Is that a problem ? Another keynote/openspace ?

• Expectations that the workforce can keep up with all
these new technologies is unrealistic

https://circleci.com/blog/its-the-future/

0-day Software
… put in production
Term taken from Kris Buytaert

What happened in 2008 ?
Euca, Openstack, CloudStack, Kubernetes, Lambda

Open Source Now
• Every vendor is doing OSS

• OSS conferences very vendor driven (except DoD and
FOSDEM)

• Explosions of tools because we all share (good)

• Software go viral thanks to social media echo chambers

• Business model for OSS startup is harder

• Big corp can cannibalize you

DevOps
Culture
Automation

Monitoring

Sharing
@botchagalupe

Principles
• Work as a self-organizing team

• Empathy between dev and ops, no silos

• Deliver value early and continuously

• Solve customer’s problems

Agile Manifesto
“
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
”

Remember DevOps
•Not here to build cool software

•Not here to be hip

•Here to provide solutions
…while having fun…

1987, published as annex in 20th anniversary of Mythical Man-Month (1995)

VMs in Containers !
Source: http://sebgoa.blogspot.ch/2015/05/running-vms-in-docker-containers-via.html

ADAPT
•Does not mean ADOPT
•Means: develop a culture of
adaptation

Not only with the business but
also with the industry/tools

Example: Docker
• Image provenance and content

• Image size

• Image security

• Tooling (e.g Docker machine, Docker Swarm…)

• Who builds your images ?

• How are they monitored ?

• Where are the logs ?

Don’t forget
• Build solutions for your business

• Develop a culture that adapts to change

• Tools will not break your silos

• “Stay curious”

• Be critical but not a hater, don’t dismiss.

The document discusses strategies for running production services, including careful planning, extensive documentation, and good communication. It emphasizes establishing runbooks that document operational tasks and procedures. Over time, as teams grow and work expands, runbooks should be automated through scripts and tools to reduce manual effort and potential errors. Automating runbooks involves initially writing scripts for small tasks and evolving them through testing, bug fixing, and incorporating additional workflow steps. Fully automated runbooks improve reliability and allow work to be completed through execution of instructions rather than human judgement.

Design patterns for efficient DevOps processes - Rebecca Fitzhugh - DevOpsDay...DevOpsDays Tel Aviv

The document discusses design patterns for efficient DevOps processes including value stream mapping, release engineering, test automation, and change management. It provides recommendations such as collecting current state information directly, ensuring release engineers understand intended deployments, automating error-prone steps, centralizing test coordination, and making change management a priority integrated within the DevOps pipeline. Design patterns that increase efficiency include continuous delivery pipelines, testing all levels from unit to integration to functionality, and establishing different change modes to balance speed, quality, and risk.

DevOps game marshmallow challengeMurughan Palaniachari

The document describes a DevOps game called the Marshmallow Challenge where teams compete to build the tallest freestanding structure using spaghetti that can support a marshmallow on top. The game aims to teach DevOps principles like collaboration, continuous learning, and applying feedback. It discusses how different groups like kindergarten students versus business students or engineers perform. The rules and process for playing the game are provided along with learnings around integrating development, operations, testing and more.

Maintenance StabilisationZsolt Fabok

This document discusses applying lean and agile principles to maintenance teams. It provides tips for using collaboration and optimization techniques like having continuous integration and delivery, using swim lanes and a hot lane to prioritize work, ensuring defects are testable by writing test cases after reproduction, measuring lead times and cycle times, and conducting regular retrospectives to continuously improve. Leadership techniques include rotating team members between roles, meeting with them face to face weekly, and implementing a pull system to avoid interruptions from issue notifications.

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...DevOpsDays Tel Aviv

The document provides tips for marketing an open source project on GitHub. It recommends explaining the motivation and purpose of the project, researching similar existing projects, and developing the project to be easy to install, use, and contribute to. Key steps include writing a good README, publishing the project in relevant communities, and submitting it to curated lists to help users discover the project. The goal is to build an active community of contributors and users to support the long-term success of the open source project.

Debugging distributed systemsBert Jan Schrijver

This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Traffic and messages should also be inspected. The process concludes by wrapping up findings and conducting a post-mortem analysis. Key challenges in distributed systems like concurrency, lack of a global clock, and independent failures are discussed.

Skills Matter DevSecOps eXchange Forum 2022 - Software architecture in a DevO...Bert Jan Schrijver

The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. Some key points made: - DevOps principles like gradual changes, customer orientation, automation, ownership, collaboration, experimentation and continuous improvement should guide architectural decisions and processes. - The architecture should start simply and evolve iteratively based on feedback from developers and customers. - Automation, infrastructure as code, and measuring architectural decisions are important. - The team should own the architecture collaboratively and the architect must be accountable and involved.

Tech writing in a continuous deployment environmentChristine Burwinkle

Christine Burwinkle discusses how technical writers can adapt to continuous deployment, which involves frequent small releases of software features. This means writers must document pieces of work efficiently and adapt quickly to shifting designs. Writers have adapted by focusing on features over releases, using tooling to quickly change docs, creating minimal viable documentation, and reducing documentation debt. Continuous deployment also means finding the right balance of control and freedom for writers.

Devops in with the old, in with the newJan Collijs

Shifting is more than shifting leftPractiTest

Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left. Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production. This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers. – Shift-Coach, where It’s more about coaching teams. – Shift-SME, where it’s more about business savvy. – Shift-Deliver, where it’s more about the road to production www.onlinetestconf.com

Modern Messaging for Distributed SystemsAndrea Rabbaglietti

Il message-passing per più di dieci anni è stata la soluzione di riferimento per affrontare le sfide e l'implementazione di un sistema distribuito: problemi di rete, forte accoppiamento fra nodi, eterogeneità delle applicazioni (diversi linguaggi di programmazione). Questo talk tratterà le soluzioni per costruire un'architettura orientata ai servizi (SOA) ed effettuare message-passing in maniera performante ed affidabile; ripercorreremo insieme i concetti e le tecnologie principali che sono alla base dei sistemi distribuiti.

JavaLand 2022 - Debugging distributed systemsBert Jan Schrijver

This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Additional steps include inspecting traffic, attaching remote debuggers, and conducting a post-mortem analysis. Throughout the process, various tools can help with tasks like logging, testing, and network inspection. The document concludes by emphasizing the importance of understanding failure modes through experience debugging real issues with distributed systems.

Debugging distributed systemsBert Jan Schrijver

This document outlines a structured approach for debugging distributed systems. It begins with observing and documenting what is known about the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Traffic and messages should be inspected, with a focus on eliminating potential issues on the client side first. The process concludes by wrapping up with documentation of findings, impacts, and lessons learned to prevent future issues. Several tools are recommended for each step to aid in debugging distributed systems effectively.

Bringing Open-Source Practices to Your Day JobBen Coe

DevOps Picc12 Management TalkMichael Rembetsy

IWMW 2016 Collaborative usability observation workshop introNeil Allison

The document discusses a collaborative usability testing technique to involve stakeholders in user research. It recommends bringing together stakeholders to observe usability tests, prioritize usability issues observed, and agree on solutions. Participants watch 3 short test sessions, take notes on issues, then consolidate lists of top issues to agree on actions. Being involved makes stakeholders more invested in addressing usability problems. The presenter provides tips for effective collaborative testing and resources for prioritization methods.

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...DevOpsDays Austin 2014

Chef can be difficult to learn at first and may cause frustration as there is a learning curve. It is important to start small with basic cookbooks, follow tutorials, and ask questions. Over time, as experience with Chef grows, so does understanding of its capabilities. Chef is constantly evolving through an active community, and what seems challenging now will become clearer. While the learning process may involve stages of denial, anger and feeling overwhelmed, acceptance that difficulties are normal helps to appreciate Chef's power for automating infrastructure.

Api360 Summit The Automated MonolithHaufe-Lexware GmbH & Co KG

The document discusses the challenges faced when attempting to transition a monolithic application to microservices. An initial attempt to extract a single service failed due to lost test coverage, scope creep and increased complexity. Lessons were learned around the need for rapid provisioning, monitoring, deployment and automated testing. A reset was implemented with time-boxed phases, infrastructure as code using Docker, and deployment automation. This successful approach focused on stabilizing the team through an emphasis on culture, structure and technology alignment to deliver reliably on time and budget.

JavaLand 2022 - Software architecture in a DevOps worldBert Jan Schrijver

The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. Some key points made are: 1) DevOps principles like gradual changes, customer orientation, automation, ownership, collaboration, experimentation and continuous improvement can be applied to software architecture practices. 2) Architects should focus on the business needs, involve developers as stakeholders, evolve architectures through feedback rather than upfront design, and embrace failure through experiments. 3) Flexible architectures that can change based on needs are preferable to rigid pre-defined architectures in a DevOps context.

10 skills developers should invest in for 2014Pakorn Weecharungsan

ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR ...DevOpsDays Tel Aviv

The document discusses effectively evaluating data solutions for systems. It recommends identifying the business value and needs, such as scale and future costs. It also suggests analyzing expected performance by considering the solution's purpose, resource requirements, and resilience. Additionally, it advises overseeing future plans like the system's scale support, R&D growth plan, and learning curve. The overall document provides guidance on comprehensively evaluating data solutions by examining business value, performance, and future oversight.

Building effective dev ops engineering culture newRovshan Musayev

Rovshan Musayev, a DevOps engineer, presents on building effective DevOps engineering culture. DevOps aims to automate processes between software development and operations teams to build, test, and release software faster and more reliably. Historically, these teams operated in silos with poor collaboration, whereas DevOps values breaking down silos through practices like infrastructure as code, continuous integration, deployment, and automation. Effective DevOps principles include collaboration between Dev and Ops, empowering autonomy, learning from mistakes, and prioritizing tasks. People are prioritized over processes and tools in the DevOps methodology.

Practical Methods for Adopting DevOps - Michael StahnkePuppet

The document outlines 5 methods for adopting DevOps practices in large organizations with siloed IT teams: 1) Standardize variable infrastructure to reduce failures, 2) Break down silos through collaboration between teams, 3) Share knowledge of failures to prevent recurrences, 4) Experiment with new tools and processes in test environments, 5) Continuously improve processes by addressing root causes rather than symptoms. The methods advocate reducing variability, integrating operations into software development, conducting root cause analyses, and allowing engineers to experiment.

Mini LeSS HugeXudong Yu

The document describes a framework called Mini LeSS Huge used for large-scale Scrum development with multiple teams. It has the following key aspects: - Uses Scrum and LeSS principles with 10 developers split across backend and frontend teams. - Features a single product backlog, product owner, and sprint planning meetings to coordinate work across teams. - Implements "feature teams" where each team works on user stories from end-to-end rather than separating tasks. - Emphasizes continual review of working software, collaboration between teams, and feedback from stakeholders to ensure successful delivery each sprint.

Beyond Agile SoftwareGabriel Hamilton

Principles of Continuous Delivery and DevOpsBert Jan Schrijver

The document discusses principles of continuous delivery (CD) and DevOps. It defines CD as integrating work frequently through automated builds and tests so software can be released at any time. DevOps is described as development and operations teams working together across the entire product lifecycle to quickly and reliably deliver higher quality software. The document provides examples of how not to implement DevOps and emphasizes that CD and DevOps are about culture, freedom, responsibility and empathy rather than just tools or processes.

Put "fast" back in "fast feedback"Lars Thorup

One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions: - Do we get all test results in less than 5 minutes after a commit? - Is our code coverage more than 75% for both front-end and back-end? - Can we start exploratory testing in less than 15 minutes after a commit? - Do all our tests pass more than 90% of our commits? This talk will give you practical advice on how to get to "yes, we get fast feedback".

Going faster with kanbanJez Halford

The document discusses the Kanban methodology for managing software development projects. It begins by explaining what Kanban is and its origins. It then outlines the key Kanban principles of visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and continuously improving. Examples are provided of how to implement these principles using a Kanban board. Advanced techniques like epic clustering and swim lanes are also covered. Tips are given on getting started with Kanban and allowing it to evolve over time.

DevOps IRL  - Jason Grimes - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

Jason Grimes is a DevOps champion and site reliability engineer who has worked in the field for over 20 years. In this presentation, he discusses Concur's DevOps journey from waterfall releases every 9-18 months to continuous delivery using microservices. He emphasizes building great teams over toolsets, adopting a growth mindset, and focusing on measuring customer experience through metrics like Apdex. Grimes also stresses the importance of sharing knowledge through local meetups and conferences to continuously level up operations.

Fake it till you make it - Keren Barzelai - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

More Related Content

What's hot (20)

Devops in with the old, in with the newJan Collijs

Shifting is more than shifting leftPractiTest

Modern Messaging for Distributed SystemsAndrea Rabbaglietti

JavaLand 2022 - Debugging distributed systemsBert Jan Schrijver

This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Additional steps include inspecting traffic, attaching remote debuggers, and conducting a post-mortem analysis. Throughout the process, various tools can help with tasks like logging, testing, and network inspection. The document concludes by emphasizing the importance of understanding failure modes through experience debugging real issues with distributed systems.

Debugging distributed systemsBert Jan Schrijver

Bringing Open-Source Practices to Your Day JobBen Coe

DevOps Picc12 Management TalkMichael Rembetsy

IWMW 2016 Collaborative usability observation workshop introNeil Allison

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...DevOpsDays Austin 2014

Api360 Summit The Automated MonolithHaufe-Lexware GmbH & Co KG

JavaLand 2022 - Software architecture in a DevOps worldBert Jan Schrijver

10 skills developers should invest in for 2014Pakorn Weecharungsan

ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR ...DevOpsDays Tel Aviv

Building effective dev ops engineering culture newRovshan Musayev

Practical Methods for Adopting DevOps - Michael StahnkePuppet

Mini LeSS HugeXudong Yu

Beyond Agile SoftwareGabriel Hamilton

Principles of Continuous Delivery and DevOpsBert Jan Schrijver

Put "fast" back in "fast feedback"Lars Thorup

Going faster with kanbanJez Halford

Devops in with the old, in with the newJan Collijs

Shifting is more than shifting leftPractiTest

Modern Messaging for Distributed SystemsAndrea Rabbaglietti

JavaLand 2022 - Debugging distributed systemsBert Jan Schrijver

Debugging distributed systemsBert Jan Schrijver

Bringing Open-Source Practices to Your Day JobBen Coe

DevOps Picc12 Management TalkMichael Rembetsy

IWMW 2016 Collaborative usability observation workshop introNeil Allison

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...DevOpsDays Austin 2014

Api360 Summit The Automated MonolithHaufe-Lexware GmbH & Co KG

JavaLand 2022 - Software architecture in a DevOps worldBert Jan Schrijver

10 skills developers should invest in for 2014Pakorn Weecharungsan

ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR ...DevOpsDays Tel Aviv

Building effective dev ops engineering culture newRovshan Musayev

Practical Methods for Adopting DevOps - Michael StahnkePuppet

Mini LeSS HugeXudong Yu

Beyond Agile SoftwareGabriel Hamilton

Principles of Continuous Delivery and DevOpsBert Jan Schrijver

Put "fast" back in "fast feedback"Lars Thorup

Going faster with kanbanJez Halford

Viewers also liked (6)

DevOps IRL  - Jason Grimes - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

Fake it till you make it - Keren Barzelai - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Av...DevOpsDays Tel Aviv

The document discusses eToro's use of CI/CD pipelines on Windows environments. It describes eToro's legacy technology stack including over 130 services running on 500 servers across two data centers. It then outlines eToro's use of Jenkins to orchestrate CI/CD flows across different environments and languages, using tools like Puppet, Mcollective, PowerShell and the Azure SDK for provisioning, deployment and orchestration. The document presents eToro's hybrid use of Microsoft technologies alongside open source tools like Redis, RabbitMQ and HAProxy to support their social investment network platform.

Leading DevOps Teams - Ben Rockwood - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

This document discusses how to lead DevOps teams by focusing on five key areas: diversity, vision, strategy, management, and tools. It emphasizes that culture emerges from these factors. Diversity of thought and new ideas are important for innovation. A shared vision and aligned strategy allow individuals to rally around a cause and unlock passion and energy. Management involves directing individuals and assets to execute the strategy. Tools should continuously improve organizational processes. The employee lifecycle is also examined, noting the importance of attraction, recruitment, onboarding, development and retention at each stage.

It's not just about the t-shirts - Sharone Zitzman - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

The document discusses the challenges faced by open source project maintainers, including having to respond to many user questions and issues while also balancing personal life. It notes how open source maintainers volunteer their own time yet are responsible for software relied on by many organizations. The document advocates redefining what is considered "cool" to recognize the important work of open source maintainers in enabling new technologies and markets.

Monitoring "unknown unknowns" - Guy Fighel - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

This document discusses monitoring systems for unknown unknowns using machine intelligence. It suggests that observability goes beyond just monitoring and instrumentation to make systems debuggable and understandable. It outlines several techniques machines could use like anomaly detection, predictions, external knowledge, recommendations, and auto-correlations. The goal is to develop an "observability quadrant" like the Johari window to better understand systems with imperfect outputs. It recommends choosing the right tools, applying common schemas to event data, using techniques like fuzzy logic and similarity checks, and focusing first on simple correlations and time series models before building complex classifiers. The best practices are to start using such techniques in production by getting feedback and continually re-evaluating relevance.

DevOps IRL  - Jason Grimes - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

Fake it till you make it - Keren Barzelai - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

CI/CD on Windows-Based Environments - Noam Shochat, eToro - DevOpsDays Tel Av...DevOpsDays Tel Aviv

Leading DevOps Teams - Ben Rockwood - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

It's not just about the t-shirts - Sharone Zitzman - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

Monitoring "unknown unknowns" - Guy Fighel - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv

Similar to How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Aviv 2017 (20)

Lean methodology sfd szeged 2011Kristof Van Tomme

stackconf 2023 | Better Living by Changing Less – IncrativeOps by Michael Cot...NETWAYS

DevOps has always been about dramatic changes to improve IT. You don’t only need to use a different set of tools, you need to change your entire IT culture! It’s all exhausting, really. Worse, this imperative to change never goes away. Will we ever actually be done and “be like Google”? Instead of carrying the flag of “change or die,” this talk proposes an alternate, more practical, sustainable, and comforting approach to improving: IncrativeOps.

Closing the Cloud Skills GapScott Lowe

From Silos to DevOps: Our StoryGil Irizarry

The Lost Tales of Platform Design (February 2017)Julien SIMON

Herding cats in the CloudDewey Sasser

Dewey Sasser discusses maintaining operational sanity in a cloudy DevOps world for a major gaming company that has transitioned all its services to public clouds like AWS. The company aims for 100% uptime and no maintenance downtime using a model where development teams are responsible for their services and a central cloud team provides shared tools and best practices. Key aspects are automated user access control using rules and workflows, tagging for cost control, and putting power in developers' hands while keeping responsibility with their teams.

PMI Thailand: DevOps / Roles of Project Manager (20-May-2020)Gonzague PATINIER

DevOps seems to be the latest ‘buzzword’ and trend in the IT industry. This is driven by business needs for ever-faster deployment of new functionality and frustrations with the time and effort it takes to get new systems into operations. It is no longer a question of ‘should we adopt DevOps’, but ‘when and how’? DevOps represents a significant cultural and behavioral change and many organizations fail to address this in their adoption. Gartner defines DevOps as a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. These culture changes include organization changes, impacting structure, roles and responsibilities. What and where is the role of the project manager in organizations that have transitioned towards adopting DevOPs? Join us and let’s discuss DevOps and answer your questions followed by an informative discussion.

OS Accelerate London - 09/16/15Appnovation Technologies

Agile.. and then? – Enterprise DevOps: the digital transformation of the IT...Peter Muryshkin

Learn how DevOps can help ITSM to access the strategic value envelope available for the digital transformation of the enterprise. Today, ITSM has to deal with many new, disruptive things. Digital transformation should be a key asset in the transformational leadership portfolio. For the enterprise IT, DevOps can be the cross functional common language and the toolkit to make the IT part of this transformation.

APIdays Paris 2018 - Cloud computing - we went through every steps of the Gar...apidays

This document summarizes a presentation about cloud computing trends and the hype cycle. It discusses both the promises and fears around cloud adoption, as well as going through each stage of the hype cycle from the technology trigger to peak expectations to disillusionment to productivity. Key points discussed include the responsibilities that shift between on-premise, IaaS, PaaS and CaaS models, challenges around integration, resiliency, reversibility and vendor lock-in, and the importance of people and processes over just technology. The conclusion emphasizes the need for subtle choices around balancing control and outsourcing as well as periodically reassessing one's cloud strategy as the landscape evolves.

Approaching risk management with your head in the cloudCompatibL Technologies ltd

CompatibL is a leading provider of custom software and risk management solutions. Chief Operating Officer Olga Orekhvo discusses how the cloud has become an integral part of CompatibL's solutions while still requiring custom development. She describes how CompatibL combines quantitative and engineering skills to create efficient solutions, develops software from the ground up to seamlessly integrate, and works closely with customers throughout the process. Orekhvo also explains how the cloud provides benefits like flexibility, cost savings, and security that are valuable for companies in a post-pandemic setting.

5-10-15 years of Java developer career - Warszawa JUG 2015Wojciech Seliga

From open source labs to ceo methods and advice by sysferafOSSa - Free Open Source Software Academia Conference

This document outlines the process of industrializing an open source software and selling it as a product. It discusses securing the intellectual property of the code, improving development practices through version control, continuous integration, testing and documentation. It also covers challenges of determining customer needs when no existing market exists, balancing innovation and technical capabilities with market demands, and the importance of user satisfaction over technical features alone. The conclusion reflects on how research labs can foster innovation and how 13 jobs have been created by building a company around code originally developed through academic research.

DevOps for Defenders in the EnterpriseJames Wickett

The document discusses how DevOps, security, and information security practices can integrate. It argues that Agile, DevOps, and continuous delivery approaches optimize for delivering value quickly by addressing perceptions of what is probable. Information security has traditionally been separate but can now integrate into the software development pipeline to provide value. Automating security testing and integrating it into build pipelines allows information security to catch up to modern software development practices.

DevOps The Cultural revolutionSomenath Ghosh

De facto DevOps, de facto Agile. Today DevOps is the Manufacturing Revolution of Our Age. There is no escape for us. When got a DevOps, you got a DevOps. DevOps simply is the combination of cultural philosophies,practices,and tools that increase an organization’s ability to deliver applications and services at high velocity : evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.

Not actually a DevOps TalkVMware Tanzu

This document provides an overview of digital transformation and adopting DevOps practices. It discusses how company lifespans have shortened and survival is not mandatory if companies do not change. It highlights examples of large companies adopting DevOps successfully, including improving productivity by 40% and reducing incident times. It emphasizes adopting a platform to standardize services and break down silos, piloting with low-risk apps, and managing change through internal marketing and pairing across roles. The document is presented by Cote, a director of marketing at Pivotal, and provides references to support its points.

WinOps Conf 2016 - Matteo Emili - Development and QA Dilemmas in DevOpsWinOps Conf

The quick rise of Continuous Delivery in the enterprise means that common problems are often approached the other way round. Concepts like Feature Flags and Testing In Production caused several headaches to developers and QA engineers, especially where they have a wealth of experience about traditional development. There are some challenges and approaches which are very common, and they still scare newcomers. Let's have a look at a few of these, with the most common solutions.

Serverless Toronto helps StartupsDaniel Zivkovic

Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success! In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA

IoT to Cloud the DevOps WayMark Heckler

The number of connected devices is growing at an accelerated pace. We developers must have the knowledge & skills to help make that happen. But how? As device deployments and data collected grow exponentially, DevOps is the answer to fast, consistent, and sane systems, organizations, and developers. This session will provide a brief-but-thorough examination of key DevOps tenets and how they apply to large-scale deployments of small-scale devices and the platforms that tie them together. A live-coding demo will convert these concepts from ideas to implementations.

Evolving to Cloud-Native - Nate Schutta 1/2VMware Tanzu

The document discusses evolving applications to be cloud native by taking advantage of cloud computing abilities like scaling up and down on demand. It describes that cloud native applications are defined by practices like continuous delivery, containers, microservices, and functions. It also discusses how infrastructure has shifted from custom servers to commodity servers and cloud providers, and how applications need to be designed to leverage this shift through principles like loose coupling, statelessness, and deploying configurations separately from code.

Lean methodology sfd szeged 2011Kristof Van Tomme

stackconf 2023 | Better Living by Changing Less – IncrativeOps by Michael Cot...NETWAYS

Closing the Cloud Skills GapScott Lowe

From Silos to DevOps: Our StoryGil Irizarry

The Lost Tales of Platform Design (February 2017)Julien SIMON

Herding cats in the CloudDewey Sasser

PMI Thailand: DevOps / Roles of Project Manager (20-May-2020)Gonzague PATINIER

OS Accelerate London - 09/16/15Appnovation Technologies

Agile.. and then? – Enterprise DevOps: the digital transformation of the IT...Peter Muryshkin

APIdays Paris 2018 - Cloud computing - we went through every steps of the Gar...apidays

Approaching risk management with your head in the cloudCompatibL Technologies ltd

5-10-15 years of Java developer career - Warszawa JUG 2015Wojciech Seliga

From open source labs to ceo methods and advice by sysferafOSSa - Free Open Source Software Academia Conference

DevOps for Defenders in the EnterpriseJames Wickett

DevOps The Cultural revolutionSomenath Ghosh

Not actually a DevOps TalkVMware Tanzu

WinOps Conf 2016 - Matteo Emili - Development and QA Dilemmas in DevOpsWinOps Conf

Serverless Toronto helps StartupsDaniel Zivkovic

IoT to Cloud the DevOps WayMark Heckler

Evolving to Cloud-Native - Nate Schutta 1/2VMware Tanzu

More from DevOpsDays Tel Aviv (20)

GRAPHQL TO THE RES(T)CUE, ELLA SHARAKANSKI, SaltoDevOpsDays Tel Aviv

The document discusses GraphQL as an alternative to REST APIs. It begins by describing some common issues with REST APIs, such as over-fetching and under-fetching data. It then introduces GraphQL as a query language that allows clients to get precisely the data they need in a single request. Key benefits of GraphQL include no breaking changes, no over-fetching or under-fetching, and being transport agnostic. The document also covers GraphQL concepts like schemas, queries, mutations, and errors. It provides examples of how problems like rate limiting and error handling are approached differently in GraphQL compared to REST. In the end, it acknowledges that GraphQL has a learning curve but can help solve real problems for

MICROSERVICES ABOVE THE CLOUD - DESIGNING THE INTERNATIONAL SPACE STATION FOR...DevOpsDays Tel Aviv

Robert Barron discusses the construction and operation of the International Space Station (ISS). The ISS was built in stages over many flights from 1998-2011, with modules being delivered and assembled to create the permanently inhabited outpost in space. It currently consists of multiple modules from the US, Russia, Europe, Japan and Canada which provide living quarters, research labs, docking ports, and more. Managing resources like oxygen generation and spacesuits on the ISS requires redundant systems to ensure resiliency in the challenging space environment.

THE (IR)RATIONAL INCIDENT RESPONSE: HOW PSYCHOLOGICAL BIASES AFFECT INCIDENT ...DevOpsDays Tel Aviv

Have you ever felt you took every wrong turn possible in the process of mitigating a production incident? Did you go through a 3-hour hell during incident response and felt the incident wasn’t complex enough to justify the horrors you’ve experienced? Did it cause you to question your engineering or problem-solving skills? Well, it’s only partially you. Our brain is wired to make decision-making simpler. In doing so, it exposes itself to biases, heuristics, and other quirks that may seem like “bad decisions” in hindsight. In this talk, through real-life outages, we’ll project those psychological principles onto the world of production monitor, and incident management. As a responder, you’ll learn why those behavioral patterns emerge during production incidents and what can be done to limit their effect, and as a manager, you’ll learn how to enable and encourage a healthy environment to better support those patterns.

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDogDevOpsDays Tel Aviv

The word observable entered the English language roughly 400 years ago, but the concepts of what it means to see, comprehend, and understand something have been debated since time immemorial. Starting in the 19th century, a series of postulates and criteria coalesced into control theory, and it is from this body of knowledge that we gained the word “observability”. Today, with the advent of complex, interconnected computer systems, that word has taken on new meanings and connotations—some useful, some detrimental, and some just plain confusing. In this talk, we’ll mix a little history, a touch of philosophy, and a healthy dose of reality, to demystify what observability means to us as professional computer people. We’ll tear through the marketing material and unearth foundational principles that will help us to build better infrastructure, write better software, and promote healthier business practices. Finally, we’ll explore some potential new avenues for discussion and understanding.

NUDGE AND SLUDGE: DRIVING SECURITY WITH DESIGN // J. WOLFGANG GOERLICH, Duo S...DevOpsDays Tel Aviv

Security people say users are the weakest link. But are they? When complying with security becomes too burdensome, users take shortcuts, find workarounds, and end up jeopardizing security. Blaming users is lazy and easy. Making security usable is time consuming and challenging. How does design research help us understand our customers? What patterns and principles drive secure behavior? How can we build empathy with customers and make the right thing to do the easiest thing to do? This session explores these questions, and provides examples of how design thinking and research can help us be more secure. We will walk through our creation of core user personas, design principles, and how these inform and direct our design choices and intent. Don’t blame your users anymore. Come learn how to be part of a future where usability leads security.

(Ignite) TAKE A HIKE: PREVENTING BATTERY CORROSION - LEAH VOGEL, CHEGGDevOpsDays Tel Aviv

This is for you, you rockstar, ninja coffee drinking workaholic who doesn’t know what a vacation day looks like. Even though you love your job and are dedicated and are super important, you need a break too. We tend to think that working all the time is an effective practice while the truth is that finding the time for self care and recharging your batteries is beneficial for both you and your company. Additionally, if you’re a leader, you’re responsible for the wellbeing of your team. In this talk I’ll discuss the importance of taking time off of work and creating a positive culture surrounding vacation time.

BUILDING A DR PLAN FOR YOUR CLOUD INFRASTRUCTURE FROM THE GROUND UP, MOSHE BE...DevOpsDays Tel Aviv

This is a story about taking the cloud infrastructure of a successful company, that is still managed as infrastructure of a startup company, and rebuilding it to support the growing business requirements, especially around disaster recovery and business continuity. In the session I will share Next Insurance’s journey - where we started, where we are now and what we learned on the way so far. I will talk about how we managed to build our proven DR plans, and actually execute them in our DR drills. I will also talk about why we decided that the only way to prove your DR plan works is to continue running your business in the DR account and make it your production account, and go on to build your next DR account. If you are a part of a company that is about to embark on a similar journey, this session might equip you with some very useful insights on how to think about such a challenge, and some very useful and practical tips on how to execute it.

THE THREE DISCIPLINES OF CI/CD SECURITY, DANIEL KRIVELEVICH, Cider SecurityDevOpsDays Tel Aviv

CI/CD pipelines are quickly becoming the path of least resistance for would-be attackers into sensitive internal systems, gaining access to critical data, with minimal effort. In the InfoSec world when we talk about CI/CD security often times this focuses on specific aspects of securing your pipeline - scanning the code, protecting secrets, securely managing code deployments, or even authentication and authorization mechanisms, but we rarely talk about all of these together. After years of being in the trenches and realizing that the attack surface is growing and the threat landscape becoming more and more complex, it has become increasingly apparent that security teams need to adapt and modify strategies to keep up with the new reality of CI/CD protection, without compromising developer velocity. In this talk I would like to propose a new way of thinking about CI/CD security - that encompasses the three disciplines that comprise CI/CD security - security in the pipeline, of the pipeline, and around the pipeline. Partial coverage of any or all of these disciplines simply will not cut it with the continuously evolving risk landscape. Security engineers need to address each of these aspects in their entirety to provide the full scope of coverage that modern organizations need, and I will take a deep dive on the challenges each introduce, and the approaches and techniques for mitigating them based on adversarial sec research.

THE PLEASURES OF ON-PREM, TOMER GABELDevOpsDays Tel Aviv

The last two decades have been all about SaaS, with advantages that cannot be overstated. Except SaaS isn’t always an option, nor is it always the right choice: businesses in tightly regulated industries, or where information security is paramount, for example, will not - often can not - consider any software that isn’t under their control. For many software enterprises, this leads to the dreaded inevitability of on-premise deployment. Fortunately, the situation today is dramatically different to a scant few years ago, let alone a decade or two: the same technologies that enable SaaS have also radically transformed on-prem deployment. Modern tools like Docker, Consul, ELK and Kubernetes - to name a few - can be leveraged to completely transform the experience for both customers and vendors. In this talk we’ll contrast the challenges and advantages of SaaS and on-prem, see how things have evolved in recent history, and see how modern on-prem deployment can be, if not pleasurable, at least relatively painless.

CONFIGURATION MANAGEMENT IN THE CLOUD NATIVE ERA, SHAHAR MINTZ, EggPackDevOpsDays Tel Aviv

Configuration Management is at the core of Ops. It’s the biggest enabler of any compute operation, small and big. In the past decade, we have switched from thinking about the machines we are configuring, to think about the software and services we are controlling. With that change of mindset, so did the tools we are using. Traditional tools like Puppet, chef, salt and Ansible are slowly declining while new tools such as Terraform, Pulumi, Helm and Kustomize are on the rise. In this talk I will try to describe the pain-points and the opportunities of this transformation as well as suggesting a future direction based on tools developed at the big-tech companies (Mainly facebook and google).

SOLVING THE DEVOPS CRISIS, ONE PERSON AT A TIME, CHRISTINA BABITSKI, DeveleapDevOpsDays Tel Aviv

We all know how hard it is to find DevOps engineers, and creating a diverse team despite gender and ethnicity bias? Nearly impossible. At this talk we will show our tools and methods implemented in the Develeap hiring process that overcome this inherited bias. About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...DevOpsDays Tel Aviv

Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors. With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).

HOW TO SCALE YOUR ONCALL OPERATION, AND SURVIVE TO TELL, ANTON DRUKHDevOpsDays Tel Aviv

“Being oncall sucks. But it doesn’t have to!” We all heard this one before. Why is it though, that oncall still remains the biggest scar for many? What can a modern Engineering org do to rein the oncall dragons, and actually help people grow as professionals as they go oncall? In this talk, I will present the main reasons why oncall is difficult in modern orgs, and describe ways to mitigate these hardships. The idea is that oncall is often the ‘backroom’ of an org, where all the technical and organizational debt take their toll. Be it unwieldy systems or broken processes between teams, oncall checks all the ‘weak boxes’. Therefore, the only way to win at oncall is to sort out your debts, starting with the organizational ones. I will dive into the detail of the oncall rotation at Snyk as the org scaled from 1 to 220 people, what worked well about it, and what was less than perfect. I will discuss the decisions made to turn oncall into a building block of the org, and show a path to rein oncall in your organization as well.

HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearBDevOpsDays Tel Aviv

Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks. This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example: Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira. You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have. You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, IcingaDevOpsDays Tel Aviv

Do you know what it feels like to navigate as someone who can’t distinguish between green and red - looking at those badges that tell you whether something is broken or a-okay? I’ll give you a quick look into what it feels like with some examples from the monitoring tool Icinga Web 2. We all tend to forget, that not everyone sees the world like we do. In this talk I’ll be walking you through different views in Icinga Web 2 with side-by-side comparisons for the default views and how different kinds of vision impairments affect those. The talks also features a few suggestions on how to improve colour schemes and making websites and webapps better to navigate with screen readers!

(Ignite) WHAT'S BURNING THROUGH YOUR CLOUD BILL - GIL BAHAT, CIDER SECURITYDevOpsDays Tel Aviv

Recent years have exposed startups to a major plague - cloud overspend. No vaccine appears to exist, plethora of tools and consultants fail to stop the bleeding. And yet, some companies manage to stay safe. What makes them different? Is it the tools? Is it the mindset? Is it developer training? In this session we will examine the cultural factors involved in sound and responsible financial management in the cloud. We will also look at relevant system design elements and product design elements which enable us to spend wisely while our business runs smoothly. Following this session, you should be better versed in cost-aware system design and some of the cultural and structural requirements to keeping your cloud bill low.

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.ioDevOpsDays Tel Aviv

In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism? WIIFM “Without data, you’re just another person with an opinion” - W. Edwards Deming SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process. Let’s talk about the importance of good SLOs and how they can help us improve our day2day

ONBOARDING IN LOCKDOWN, HILA FOX, AuguryDevOpsDays Tel Aviv

In this talk, I will share do's and don'ts on how to onboard successfully in a remote or hybrid setup including moving to a leadership role, speaking from my own journey onboarding remotely in the midst of a global pandemic. I will share the tips that worked for me for successful onboarding, how I was able to be productive, impactful, and make a good impression on others. The key issues as an “onbordee” that I will talk about are how to create relationships, make yourself visible in the company, time management, and more. Since I started working in Augury over 100 new employees have joined the company. Each month I give a session that is part of their general onboarding process. This became a crucial step due to the fact that we are now a hybrid company and a lot of people are onboarding remotely or in a hybrid setup for the first time in their lives. I joined the company as a backend developer and a few months into my role, the squad leader position in my squad was up for grabs and I was fortunate enough to grab it :) This is my first official leadership role, which I also needed to onboard into in a hybrid setup. I will share the process that I built for myself on “How to lead”. Also, a word or two on the process we built as a squad on how we work in a hybrid setup, what are we optimizing for when we do meet and how to include new members of the team.

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, FireflyDevOpsDays Tel Aviv

In your ever-changing Infrastructure, some changes are intentional while others are not. Drift is what happens whenever the real-world state of your infrastructure differs from the state defined in your configuration. This can happen for many reasons, sometimes it happens when adding or removing resources, other times when changing resource definitions upon resource termination or failure, and even when changes have been made manually or via other automation tools. While Terraform itself can detect drifts, in most cases, you will be informed about it too late: just before you are about to deploy new changes to your infrastructure. What’s interesting about Terraform though, is that you can apply changes in two separate and distinct steps of “Planning” and “Applying”. This means that you have full visibility of what Terraform is planning on doing beforehand, and if you are satisfied with the changes, you can choose to apply them. So how does this work? When something is changed intentionally, it will appear in the source code, and the Terraform plan will not do anything. However, if any part of the infrastructure has been changed manually, Terraform’s plan will identify this, and alert you to the change. In other words, if your IaC drifted from its expected state, then Terraform’s plan will, in fact, detect it. Applying this simple solution can empower DevOps and developer velocity, with the reassurance and context for unexpected changes in your IaC, in near real-time. This talk will showcase real-world examples, and practical ways to apply this in your production environments while doing so safely and at the pace of your engineering cycles.

KEYNOTE | WHAT'S COMING IN THE NEXT 10 YEARS OF DEVOPS? // ELLEN CHISA, bolds...DevOpsDays Tel Aviv