DevOps in the Real World
0 likes135 views
The document discusses DevOps practices for real world companies. It defines DevOps as people, processes and tools working together to enable continuous delivery of value to end users faster. It provides advice on establishing baselines, starting simple with one codebase, automating tests and infrastructure, implementing feature flags, improving cycle times through automation and removing bottlenecks, and shifting to a no-silos culture with collaboration between teams. The overall message is that DevOps requires cultural and operational changes to break down barriers and deliver value to users faster.
1 of 59
Download to read offline
Ad
Recommended
Jira and Confluence - How the company behind those products works - Anatoli K...
Jira and Confluence - How the company behind those products works - Anatoli K...Dominic Trần The document introduces Anatoli Kazatchkov, a Confluence development manager at Atlassian with 11 years of software development experience. It then summarizes several Atlassian products like JIRA, Confluence, Bamboo, FishEye & Crucible, and Stash. The document discusses when each product would be used and also covers development roles, problem roles, customer roles, and tips for getting software out the door like tracking issues, using version control, writing automated tests, and releasing often.
Completely Test-Driven
Completely Test-DrivenIan Truslove This presentation outlines the philosophy, concepts and tools your team needs to completely test drive your products efficiently, from the front end down. It will define what unit tests and TDD are, and cover acceptance testing and ATDD with Cucumber, behavior driven development (BDD) and various test structures, mock objects, and fluent matchers.
My Little Webap - DevOpsSec is Magic
My Little Webap - DevOpsSec is MagicApollo Clark The document discusses the DevOpsSec approach which aims to integrate security testing into the development process through automation. It outlines how DevOpsSec can help address issues that arise from the traditional separation of development and operations teams. The document provides examples of different types of tests that can be automated, such as unit testing, performance testing, and security testing of an application's attack surface. It promotes automating as many tests as possible and sharing test automation code to continuously monitor for vulnerabilities and issues.
Enabling your DevOps culture with AWS-webinar
Enabling your DevOps culture with AWS-webinarAaron Walker In this presentation shows you how the benefits of AWS technologies can be combined with a new approach to Development and Operations.
It’s all about delivering new features and functionality faster, without compromising reliability, stability and performance.
* Understand the challenges faced by traditional Development and Operations teams
* Apply Continuous Integration/Delivery processes and tools to enable change
* Appreciate how various AWS technologies can be used to facilitate DevOps
Continuous database deployment
Continuous database deploymentMike (Michael) Acord This presentation discusses continuous database deployments. It begins with an introduction of the presenter and an overview of topics to be covered. It then contrasts manual database change management with continuous deployment. The main methods covered are schema-based, using the database schema in source control; script-based, using change scripts; and code-based, coding database changes. Benefits include reduced errors and faster releases. Best practices discussed include backing up data and deploying breaking changes in steps. The presentation concludes with a call for questions.
Continuous Delivery at Wix, Yaniv Even Haim
Continuous Delivery at Wix, Yaniv Even HaimDevOpsDays Tel Aviv We will go over the motivations for wix.com R&D to move to a CI/CD/TDD model, how the model was implemented and the impact on Wix R&D. We will cover the tools used (developed in-house and 3rd party), change in methodologies, what we have learned during the transformation and the unexpected change in working with product and the rest of the company.
Presented in the Continuous Delivery track at DevOps Con Israel 2013
DevOpsDays Silicon Valley 2014 - The Game of Operations
DevOpsDays Silicon Valley 2014 - The Game of OperationsRandy Shoup Operating online games is fun and challenging. Games are some of the spikiest workloads around, and real-time really means *real-time*. Randy shares many of the DevOps techniques his team has put into practice at KIXEYE: Cloud infrastructure, Service teams, and DevOps Culture. He talks about elastic workloads, micro-services, configuration automation, and a common service "chassis". He further discusses the organizational and technical disciplines of team autonomy, internal vendor-customer relationships, and, of course, "you build it, you run it"!
#ESPC18 How to do #devops with the #SharePoint Framework and why it matters?
#ESPC18 How to do #devops with the #SharePoint Framework and why it matters?Vincent Biret 1) The document discusses how to do DevOps with the SharePoint Framework including introducing the new tooling stack for SPFx, the software development lifecycle, and Visual Studio Team Services for source control and automation.
2) It demonstrates how to set up build pipelines in VSTS to automate builds and deployments including unit testing SPFx web parts.
3) The document also discusses managing technical debt through practices like linting, static analysis, and code quality tools like SonarQube.
11 Goals of High Functioning SQL Developers
11 Goals of High Functioning SQL DevelopersIke Ellis This session focuses on what it takes to be high-functioning SQL developers in a world of continuous delivery and continuous integration.
Reactive All the Way Down the Stack
Reactive All the Way Down the StackSteve Pember Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack.
In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.
New Server in an Hour
New Server in an HourMike Hillwig This document discusses how to quickly deploy a new SQL Server instance within an hour by being well prepared. It recommends capturing configuration files, collecting existing scripts, documenting build processes, and standardizing servers for consistency and ease of delegation. The key steps are outlined as creating file paths, installing SQL, configuring, bouncing, monitoring, and rebooting. Resources for more information are also provided.
Continuous delivery with Codeship
Continuous delivery with CodeshipTetiana Chupryna How to set up continuous delivery in 15 minutes if you really need it but you don't know anything about it (my case). Talk on Sloboda studio edu session.
Greach 2018: Surviving Microservices
Greach 2018: Surviving MicroservicesSteve Pember The document discusses various topics related to surviving in a microservices environment. It begins by outlining some benefits of microservices such as reduced coupling, continuous delivery, and efficient scaling. It then covers infrastructure topics like managing logs, metrics, deployments, builds, and environments. Architecture topics discussed include overall design, technologies, testing approaches, communication methods, and data persistence. The document also addresses team communication and processes. It concludes by providing some miscellaneous advice for working with microservices.
A tale of 3 databases
A tale of 3 databasesChris Skardon This document summarizes Chris Skardon's experience migrating the database for his competition running site Tournr from SQL to document and graph databases. It describes how the initial database choice of SQL Server became limiting and led to migrations first to RavenDB, a document database, and then to Neo4j, a graph database. Both migrations required reworking the data model and code but provided performance and flexibility benefits. While challenging, the migrations were worthwhile as the graph model better fit Tournr's needs.
Seven Jobs You Should Be Running #sqlsat126
Seven Jobs You Should Be Running #sqlsat126Mike Hillwig This document discusses 7 SQL Agent jobs that should be running to monitor a SQL Server environment. It provides background on the presenter, Mike Hillwig, and introduces the topic of using SQL Agent to automate monitoring processes. Example monitoring jobs discussed include checking for auto shrink being enabled, verifying backups are running successfully, and alerting on failed SQL Agent jobs. The presentation aims to provide both introductory information on SQL Agent and specific monitoring jobs and scripts that can be implemented.
SQL Server Tips & Tricks
SQL Server Tips & TricksIke Ellis This document provides 20 tips for SQL Server performance tuning and administration from MVP Ike Ellis. The tips cover topics such as SSIS, SSAS, SSRS, query performance, indexing, partitioning, hardware troubleshooting, scripting, auditing, and more. Ellis advocates spending time on report formatting, using window functions, scripting with PowerShell, enforcing business rules in the database, and logging activities for auditing purposes. He provides various resources and links for further information.
Why Enterprises Are Embracing the Cloud
Why Enterprises Are Embracing the CloudRandy Shoup After being deeply involved in public cloud for the last several years, as both a provider and a consumer, I have been very pleasantly surprised at the rate at which large enterprises are rapidly moving to the cloud. For all the right reasons, even the most regulated and risk-averse of industries -- banking, for example -- are rapidly moving workloads out of their own owned data centers. Public cloud is not just for the "unicorns", but for the "horses" as well. This short vignette, presented at the GOTO Aarhus 2014 conference, tries to explain why this trend will continue and accelerate, and why we should be excited about it.
Cloud Shadows to Crepuscular Rays
Cloud Shadows to Crepuscular RaysAlexandra Richards The document discusses cloud computing concepts like AWS, Docker, Kubernetes, serverless computing, configuration management, and DevOps. It notes that AWS has won the hosting war but not necessarily the cloud war. Cloud provides a better way to run software compared to on-premises. Documentation is emphasized as extremely important for platforms and services. While infrastructure teams' jobs may change with cloud, their skills around operations, infrastructure and systems administration will still be needed indefinitely.
Micro Service – The New Architecture Paradigm
Micro Service – The New Architecture ParadigmEberhard Wolff The document discusses microservices as a new software architecture paradigm. It defines microservices as small, independent processes that work together to form an application. The key benefits of microservices are that they allow for easier, faster deployment of features since each service is its own deployment unit and teams can deploy independently without integration. However, the document also notes challenges of microservices such as increased communication overhead, difficulty of code reuse across services, and managing dependencies between many different services. It concludes that microservices are best for projects where time to market is important and continuous delivery is a priority.
In-house web automation?
In-house web automation?Adam Christian This document discusses various tools and approaches for automating web application testing. It covers infrastructure options like using boxes, VMs, and cloud services. It also discusses frameworks for test automation including Windmill, Selenium, WatiR, and others. The document provides examples of continuous integration tools like Hudson and ways to approach test coverage, maintenance of the automation environment, and expanding the infrastructure over time. It emphasizes that test automation can help development and QA teams while increasing reliability.
Hiep le - xp should be dead! here is why. 
Hiep le - xp should be dead! here is why. Lê Trọng-Hiệp This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
Is serverless the new swiss cheese? ServerlessDays NYC 2018
Is serverless the new swiss cheese? ServerlessDays NYC 2018Chase Douglas This document discusses some challenges with serverless development including managing infrastructure as code, collaboration mechanisms, testing, and monitoring. It outlines gaps in these areas such as permission scoping when deploying infrastructure, parameterization to avoid hardcoding secrets, testing approaches, and ensuring consistent instrumentation. The author advocates using frameworks that can automate tasks like instrumentation to help address these gaps and enable high performance serverless teams through configuration management, collaboration, and consistency.
Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...
Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...Peter Leschev A Build Engineering Team’s Journey of Infrastructure as Code - the challenges that we’ve faced and the practices that we implemented as we went along our journey.
Challenges of moving a java team to scala
Challenges of moving a java team to scalaJoão Cavalheiro Moving a Java team to Scala presents both challenges and benefits. Some challenges include Scala features like infix notation and higher order functions that can scare Java developers. It is important to select team members comfortable with functional programming concepts. Benefits include the Scala REPL for experimenting, compatibility with Java libraries and tools, and features like class constructors and pattern matching that allow for more concise code. With the right approach, a team can embrace Scala's advantages while overcoming unfamiliar elements.
Surviving in a Microservices environment -abridged
Surviving in a Microservices environment -abridgedSteve Pember Many presentations on Microservices offer a high-level view; rarely does one hear what it’s like to work in such an environment. Individual services are somewhat trivial to develop, but now you suddenly have countless others to track. You’ll become obsessed over how they communicate. You’ll have to start referring to the whole thing as “the Platform”. You will have to take on some considerable DevOps work and start learning about deployment pipelines, metrics, and logging.
Don’t panic. In this presentation we’ll discuss what we learned over the past four years by highlighting our mistakes. We’ll examine what a development lifecycle might look like for adding a new service, developing a feature, or fixing bugs. We’ll see how team communication is more important than one might realize. Most importantly, we’ll show how - while an individual service is simple - the infrastructure demands are now much more complicated: your organization will need to introduce and become increasingly dependent on various technologies, procedures, and tools - ranging from the ELK stack to Grafana to Kubernetes. Lastly, you’ll come away with the understanding that your resident SREs will become the most valued members of your team.
Speed up your Serverless development flow
Speed up your Serverless development flowEfi Merdler-Kravitz Developers arriving at the Serverless scene usually find it hard to use the previous methodologies and tools they are used to in this new arena. Why? Because you can’t run Serverless locally. Up until now, a developer could spin a container or install PostgreSQL or NGNIX on their machine and start playing. The cycle of code → build → test was reasonably fast, but now it changed, building and testing cannot run locally, they have to run in the cloud which causes developers to lose productivity.
How do we change it? How do we keep the same productivity levels while enjoying the benefits of Serverless.
The following session will cover:
Reasons for a slow development cycle in Serverless environments
Tips and tricks for speeding up the development flow
Micro Services - Smaller is Better?
Micro Services - Smaller is Better?Eberhard Wolff This presentation shows some advice how to be successful with micro services: Which size is right? How shall a project start? What about refactoring?
DevSecCon Asia 2017 - Abhay Bhargav: Building an Application Vulnerability To...
DevSecCon Asia 2017 - Abhay Bhargav: Building an Application Vulnerability To...DevSecCon The document discusses building an application vulnerability toolchain for SecDevOps. It advocates leveraging existing security tools like SAST and DAST scanners through automation to reuse human effort. The author describes their process of identifying how to test applications based on factors like the stack and platform. They also discuss instrumenting and testing REST APIs, building custom automation, correlating data from multiple scans and tools in a NoSQL database, and using tools like Docker, Selenium and OWASP ZAP through their APIs.
DevOps, Common use cases, Architectures, Best Practices
DevOps, Common use cases, Architectures, Best PracticesShiva Narayanaswamy This document discusses DevOps concepts and best practices. It recommends breaking down barriers between development and operations, treating infrastructure as code, automating processes, implementing continuous integration and deployment, and monitoring systems. The key aspects are adopting a collaborative culture, implementing automation tools, and establishing practices like infrastructure as code, configuration management, and continuous integration, delivery and deployment.
Ad
More Related Content
What's hot (20)
11 Goals of High Functioning SQL Developers
11 Goals of High Functioning SQL DevelopersIke Ellis This session focuses on what it takes to be high-functioning SQL developers in a world of continuous delivery and continuous integration.
Reactive All the Way Down the Stack
Reactive All the Way Down the StackSteve Pember Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack.
In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.
New Server in an Hour
New Server in an HourMike Hillwig This document discusses how to quickly deploy a new SQL Server instance within an hour by being well prepared. It recommends capturing configuration files, collecting existing scripts, documenting build processes, and standardizing servers for consistency and ease of delegation. The key steps are outlined as creating file paths, installing SQL, configuring, bouncing, monitoring, and rebooting. Resources for more information are also provided.
Continuous delivery with Codeship
Continuous delivery with CodeshipTetiana Chupryna How to set up continuous delivery in 15 minutes if you really need it but you don't know anything about it (my case). Talk on Sloboda studio edu session.
Greach 2018: Surviving Microservices
Greach 2018: Surviving MicroservicesSteve Pember The document discusses various topics related to surviving in a microservices environment. It begins by outlining some benefits of microservices such as reduced coupling, continuous delivery, and efficient scaling. It then covers infrastructure topics like managing logs, metrics, deployments, builds, and environments. Architecture topics discussed include overall design, technologies, testing approaches, communication methods, and data persistence. The document also addresses team communication and processes. It concludes by providing some miscellaneous advice for working with microservices.
A tale of 3 databases
A tale of 3 databasesChris Skardon This document summarizes Chris Skardon's experience migrating the database for his competition running site Tournr from SQL to document and graph databases. It describes how the initial database choice of SQL Server became limiting and led to migrations first to RavenDB, a document database, and then to Neo4j, a graph database. Both migrations required reworking the data model and code but provided performance and flexibility benefits. While challenging, the migrations were worthwhile as the graph model better fit Tournr's needs.
Seven Jobs You Should Be Running #sqlsat126
Seven Jobs You Should Be Running #sqlsat126Mike Hillwig This document discusses 7 SQL Agent jobs that should be running to monitor a SQL Server environment. It provides background on the presenter, Mike Hillwig, and introduces the topic of using SQL Agent to automate monitoring processes. Example monitoring jobs discussed include checking for auto shrink being enabled, verifying backups are running successfully, and alerting on failed SQL Agent jobs. The presentation aims to provide both introductory information on SQL Agent and specific monitoring jobs and scripts that can be implemented.
SQL Server Tips & Tricks
SQL Server Tips & TricksIke Ellis This document provides 20 tips for SQL Server performance tuning and administration from MVP Ike Ellis. The tips cover topics such as SSIS, SSAS, SSRS, query performance, indexing, partitioning, hardware troubleshooting, scripting, auditing, and more. Ellis advocates spending time on report formatting, using window functions, scripting with PowerShell, enforcing business rules in the database, and logging activities for auditing purposes. He provides various resources and links for further information.
Why Enterprises Are Embracing the Cloud
Why Enterprises Are Embracing the CloudRandy Shoup After being deeply involved in public cloud for the last several years, as both a provider and a consumer, I have been very pleasantly surprised at the rate at which large enterprises are rapidly moving to the cloud. For all the right reasons, even the most regulated and risk-averse of industries -- banking, for example -- are rapidly moving workloads out of their own owned data centers. Public cloud is not just for the "unicorns", but for the "horses" as well. This short vignette, presented at the GOTO Aarhus 2014 conference, tries to explain why this trend will continue and accelerate, and why we should be excited about it.
Cloud Shadows to Crepuscular Rays
Cloud Shadows to Crepuscular RaysAlexandra Richards The document discusses cloud computing concepts like AWS, Docker, Kubernetes, serverless computing, configuration management, and DevOps. It notes that AWS has won the hosting war but not necessarily the cloud war. Cloud provides a better way to run software compared to on-premises. Documentation is emphasized as extremely important for platforms and services. While infrastructure teams' jobs may change with cloud, their skills around operations, infrastructure and systems administration will still be needed indefinitely.
Micro Service – The New Architecture Paradigm
Micro Service – The New Architecture ParadigmEberhard Wolff The document discusses microservices as a new software architecture paradigm. It defines microservices as small, independent processes that work together to form an application. The key benefits of microservices are that they allow for easier, faster deployment of features since each service is its own deployment unit and teams can deploy independently without integration. However, the document also notes challenges of microservices such as increased communication overhead, difficulty of code reuse across services, and managing dependencies between many different services. It concludes that microservices are best for projects where time to market is important and continuous delivery is a priority.
In-house web automation?
In-house web automation?Adam Christian This document discusses various tools and approaches for automating web application testing. It covers infrastructure options like using boxes, VMs, and cloud services. It also discusses frameworks for test automation including Windmill, Selenium, WatiR, and others. The document provides examples of continuous integration tools like Hudson and ways to approach test coverage, maintenance of the automation environment, and expanding the infrastructure over time. It emphasizes that test automation can help development and QA teams while increasing reliability.
Hiep le - xp should be dead! here is why.
Hiep le - xp should be dead! here is why. Lê Trọng-Hiệp This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
Is serverless the new swiss cheese? ServerlessDays NYC 2018
Is serverless the new swiss cheese? ServerlessDays NYC 2018Chase Douglas This document discusses some challenges with serverless development including managing infrastructure as code, collaboration mechanisms, testing, and monitoring. It outlines gaps in these areas such as permission scoping when deploying infrastructure, parameterization to avoid hardcoding secrets, testing approaches, and ensuring consistent instrumentation. The author advocates using frameworks that can automate tasks like instrumentation to help address these gaps and enable high performance serverless teams through configuration management, collaboration, and consistency.
Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...
Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...Peter Leschev A Build Engineering Team’s Journey of Infrastructure as Code - the challenges that we’ve faced and the practices that we implemented as we went along our journey.
Challenges of moving a java team to scala
Challenges of moving a java team to scalaJoão Cavalheiro Moving a Java team to Scala presents both challenges and benefits. Some challenges include Scala features like infix notation and higher order functions that can scare Java developers. It is important to select team members comfortable with functional programming concepts. Benefits include the Scala REPL for experimenting, compatibility with Java libraries and tools, and features like class constructors and pattern matching that allow for more concise code. With the right approach, a team can embrace Scala's advantages while overcoming unfamiliar elements.
Surviving in a Microservices environment -abridged
Surviving in a Microservices environment -abridgedSteve Pember Many presentations on Microservices offer a high-level view; rarely does one hear what it’s like to work in such an environment. Individual services are somewhat trivial to develop, but now you suddenly have countless others to track. You’ll become obsessed over how they communicate. You’ll have to start referring to the whole thing as “the Platform”. You will have to take on some considerable DevOps work and start learning about deployment pipelines, metrics, and logging.
Don’t panic. In this presentation we’ll discuss what we learned over the past four years by highlighting our mistakes. We’ll examine what a development lifecycle might look like for adding a new service, developing a feature, or fixing bugs. We’ll see how team communication is more important than one might realize. Most importantly, we’ll show how - while an individual service is simple - the infrastructure demands are now much more complicated: your organization will need to introduce and become increasingly dependent on various technologies, procedures, and tools - ranging from the ELK stack to Grafana to Kubernetes. Lastly, you’ll come away with the understanding that your resident SREs will become the most valued members of your team.
Speed up your Serverless development flow
Speed up your Serverless development flowEfi Merdler-Kravitz Developers arriving at the Serverless scene usually find it hard to use the previous methodologies and tools they are used to in this new arena. Why? Because you can’t run Serverless locally. Up until now, a developer could spin a container or install PostgreSQL or NGNIX on their machine and start playing. The cycle of code → build → test was reasonably fast, but now it changed, building and testing cannot run locally, they have to run in the cloud which causes developers to lose productivity.
How do we change it? How do we keep the same productivity levels while enjoying the benefits of Serverless.
The following session will cover:
Reasons for a slow development cycle in Serverless environments
Tips and tricks for speeding up the development flow
Micro Services - Smaller is Better?
Micro Services - Smaller is Better?Eberhard Wolff This presentation shows some advice how to be successful with micro services: Which size is right? How shall a project start? What about refactoring?
Similar to DevOps in the Real World (20)
DevSecCon Asia 2017 - Abhay Bhargav: Building an Application Vulnerability To...
DevSecCon Asia 2017 - Abhay Bhargav: Building an Application Vulnerability To...DevSecCon The document discusses building an application vulnerability toolchain for SecDevOps. It advocates leveraging existing security tools like SAST and DAST scanners through automation to reuse human effort. The author describes their process of identifying how to test applications based on factors like the stack and platform. They also discuss instrumenting and testing REST APIs, building custom automation, correlating data from multiple scans and tools in a NoSQL database, and using tools like Docker, Selenium and OWASP ZAP through their APIs.
DevOps, Common use cases, Architectures, Best Practices
DevOps, Common use cases, Architectures, Best PracticesShiva Narayanaswamy This document discusses DevOps concepts and best practices. It recommends breaking down barriers between development and operations, treating infrastructure as code, automating processes, implementing continuous integration and deployment, and monitoring systems. The key aspects are adopting a collaborative culture, implementing automation tools, and establishing practices like infrastructure as code, configuration management, and continuous integration, delivery and deployment.
DevOps! What, Why and How?
DevOps! What, Why and How?Omar Fathy DevOps aims to break down silos between development and operations teams through collaboration and automation. It combines cultural philosophies and tools to help organizations rapidly deliver high quality software. Under the traditional approach, dev and ops teams worked separately with different priorities, leading to slow delivery and finger pointing when problems arose. DevOps establishes a shared culture and goals between the teams through practices like continuous integration, automated testing, and deployment pipelines. While DevOps has no single tool, many tools have emerged to support its goals, such as configuration management, containers, orchestration, and monitoring tools.
DevOps The Cultural revolution
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.
Dev ops lessons learned - Michael Collins
Dev ops lessons learned - Michael CollinsDevopsdays The document discusses lessons learned from trying to implement DevOps in a rapidly growing company. Some key lessons include: (1) being able to clearly articulate what DevOps means for both individuals and the organization; (2) trusting developers and providing them with what they need; and (3) starting DevOps efforts with a focus on development environments rather than just production. The document also emphasizes focusing on toolchains rather than individual tools, using a service delivery pipeline approach, and ensuring good communication and hiring practices.
You build it, you run it
You build it, you run itSkyscanner This document discusses the "You Build It, You Run It" (YBYR) approach where developers are responsible for the full software release cycle from defining requirements to monitoring in production. The approach aims to speed up feature delivery through faster recovery from failures and more frequent releases. While it provides benefits like fewer production failures, adopting YBYR requires cultural change and depends on context, with no single solution. Frameworks and coaching are important to implement the approach successfully over time without making things worse initially.
1st Riga DevOps meetup
1st Riga DevOps meetupUldis Karlovs-Karlovskis This document summarizes a 1st DevOps meetup in Riga. It introduces Uldis Karlovs-Karlovskis as the DevOps Evangelist and discusses what DevOps is, including that it is a culture where development and operations work together. It also notes that DevOps involves tools like Jenkins, Git, Ansible, AWS, Chef and Jira. Finally, it discusses why organizations adopt DevOps and emphasizes continual learning about DevOps through resources like books, reports and online sources.
Beyond DevOps - How Netflix Bridges the Gap
Beyond DevOps - How Netflix Bridges the GapJosh Evans Operating a massively scalable, constantly changing, distributed global service is a daunting task. We innovate at breakneck speed to attract new customers and stay ahead of the competition. Simultaneously improving service quality and enabling rapid, continuous change seems impossible on the surface.
At Netflix, Operations Engineering is a centralized organization whose charter is to accomplish just that by applying high-leverage software engineering practices like continuous delivery. real-time analytics, and automation to solve operational problems. It's well established that many traditional IT Operations teams struggle to bridge the gap with software engineering. Operations Engineering is no exception. And while DevOps as a construct seeks to address this gap, it doesn't go far enough. It does not explain how to bridge the gap or even why it's important to do so.
In this talk we’ll use Netflix Operations Engineering as a case study to address these questions. We'll explore common challenges faced by operational teams and strategies to overcome them.
Modern Software Architecture 
Modern Software Architecture Ahmed Marzouk The document discusses modern architecture and its key principles. It covers programming paradigms like object-oriented programming and functional programming and how they relate to architecture. It also discusses SOLID design principles, components, attributes of modern architecture like loose coupling and high cohesion, and patterns like domain-driven design and event sourcing. Specific architectures like microservices are mentioned. Case studies are presented and questions are posed about architectural topics.
DevSecOps - The big picture
DevSecOps - The big pictureStefan Streichsbier This document discusses the concepts of DevSecOps at a high level. It begins with a brief history of development methodologies, from Waterfall to Agile, and how Ops became a bottleneck. This led to trends in Agile Operations and collaboration between Dev and Ops, known as DevOps. DevSecOps expands this to incorporate security. It discusses the importance of culture, processes, and technologies for effective communication, automation, and collaboration across Dev, Ops, and Security. The goal is to enable organizations to deliver inherently secure software at DevOps speed through a high-trust environment and automated security pipelines integrated into the software development lifecycle.
DevSecOps - The big picture
DevSecOps - The big pictureDevSecOpsSg This document discusses the concepts of DevSecOps at a high level. It begins with a brief history of development methodologies, from Waterfall to Agile, and how Ops became a bottleneck. This led to trends in Agile Operations and collaboration between Dev and Ops, known as DevOps. DevSecOps expands this to incorporate security. It discusses DevSecOps in terms of culture, processes, and technologies, with a focus on secure software development lifecycles, security pipelines, requirements management, and automated testing and monitoring. The goal of DevSecOps is to enable organizations to deliver inherently secure software at DevOps speed.
SACon 2019 - Surviving in a Microservices Environment
SACon 2019 - Surviving in a Microservices EnvironmentSteve Pember Many presentations on microservices offer a high-level view of the architecture; rarely do you hear what it’s like to work in such an environment. Stephen Pember shares his experience migrating from a monolith to microservices across several companies, highlighting the mistakes made along the way and offering advice.
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as CodeSteve Mercier Slides from my talk at ConFoo Montreal, February 2016. A presentation on how to apply configuration management (CM) principles for your various environments, to control changes made to them. You apply CM on your code, why not on your environments content? This presentation will present the infrastructure as code principles using Chef and/or Ansible. Topics discussed include Continuous Integration, Continuous Delivery/Deployment principles, Infrastructure As Code and DevOps.
My personal story from azure it pro to azure dev ops
My personal story from azure it pro to azure dev opsnj-azure This document provides an agenda and summary for a presentation on how an Azure IT Pro embraced DevOps practices. The presentation discusses how the presenter started as an Azure IT Pro managing infrastructure, then learned DevOps practices like using Azure Resource Manager templates, infrastructure as code, and continuous deployment. It provides demos of authoring ARM templates in Visual Studio and "DevOps-ing" a web app. The presentation aims to help other Azure IT Pros adopt DevOps practices to deploy infrastructure and applications faster and more reliably.
Devops - why, what and how?
Devops - why, what and how?Malinda Kapuruge This document provides an overview of DevOps, including:
1) It discusses Garry, a product owner whose team had slow and manual software delivery processes until discovering DevOps.
2) DevOps is defined as a culture change involving shared responsibility between development and operations teams to deliver software rapidly through practices like continuous integration, delivery, infrastructure as code, and monitoring.
3) The benefits of DevOps are outlined as faster and more frequent software delivery, improved quality, security, and compliance through automation and visibility across the software lifecycle.
4) Examples of DevOps in action include deploying a web application directly from a development machine versus through an automated build and test process on a separate build box.
DevOps Overview
DevOps OverviewOmri Spector Recently I was asked to explain what dev-ops is at a large enterprise software vendor undergoing transformation.
In these slides, I present the concepts, tools and mindset that drive DevOPS.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver SoftwareChris Weldon Many project teams have adopted unit testing as a necessary step in their development process. Many more use a test-first approach to keep their code lean. Yet, far too often these teams still suffer from many of the same impediments: recurrent integration failures with other enterprise projects, slow feedback with the customer, and sluggish release cycles. With a languishing feedback loop, the enterprise continues to put increasing pressure on development teams to deliver. How does an aspiring agile team improve to meet the demands of the enterprise?
Continuous integration is the next logical step for the team. In this talk, you’ll learn how continuous integration solves intra and inter-project integration issues without manual overhead, the value added by continuous integration, and how to leverage tools and processes to further improve the quality of your code. Finally, we discuss the gold standard of agile teams: continuous deployment. You’ll learn how continuous deployment helps close the feedback loop with your customers, increases visibility for your team, and standardizes the deployment process.
DevOps: IT's Automation Revolution
DevOps: IT's Automation RevolutionIBM UrbanCode Products DevOps aims to reduce conflict between development and operations teams through improved collaboration and automation. It advocates destroying stereotypes, involving both teams in strategy, instilling process discipline, and accelerating workflows with automation. Automation can perform tasks and connect processes to reduce complexity and accelerate application deployment. Successful DevOps requires open communication across the development lifecycle and treating releases as packaged transitions rather than individual components.
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOps
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOpsSaltStack Let's set aside the buzzwords for a moment and have an honest discussion about DevOps. There is the idea of putting more Dev into Ops, but just as crucial (if not more crucial) is getting your Devs to think more like Ops. Most developers have little to no experience dealing with production environments, and helping them add value to DevOps efforts can be difficult. This talk will cover practical ways of mentoring Devs into more DevOps skills and responsibilities. Ultimately, the goal is to help your Devs gain the skills leading to better production health, application performance and uptime. Of course, we'll also consider how SaltStack can help.
The Power of Azure DevOps
The Power of Azure DevOpsJeff Bramwell Azure DevOps offers many tools that you can choose from to augment your DevOps practices. Whether you are delivering software on-prem or in the cloud, building OSS or commercial solutions, using .NET, Java, Swift or any other language, you should see what Azure DevOps has to offer.
Ad
Recently uploaded (20)
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Into The Box Conference Keynote Day 1 (ITB2025)
Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Big Data Analytics Quick Research Guide by Arthur Morgan
Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
Linux Support for SMARC: How Toradex Empowers Embedded Developers
Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how:
• Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules.
• Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance.
• Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity.
• Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications.
• Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market.
With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications.
Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market
For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
Cyber Awareness overview for 2025 month of security
Cyber Awareness overview for 2025 month of securityriccardosl1 Cyber awareness training educates employees on risk associated with internet and malicious emails
Drupalcamp Finland – Measuring Front-end Energy Consumption
Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove How to measure web front-end energy consumption using Firefox Profiler. Presented in DrupalCamp Finland on April 25th, 2025.
HCL Nomad Web – Best Practices and Managing Multiuser Environments
HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/
HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client.
Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience.
In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including
- Accessing the console
- Locating and interpreting log files
- Accessing the data folder within the browser’s cache (using OPFS)
- Understand the difference between single- and multi-user scenarios
- Utilizing Client Clocking
Cybersecurity Identity and Access Solutions using Azure AD
Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ Cybersecurity Identity and Access Solutions using Azure AD
Build Your Own Copilot & Agents For Devs
Build Your Own Copilot & Agents For DevsBrian McKeiver May 2nd, 2025 talk at StirTrek 2025 Conference.
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
Andrew Marnell: Transforming Business Strategy Through Data-Driven Insights
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
Quantum Computing Quick Research Guide by Arthur Morgan
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager API
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts!
📕 Agenda
Welcome & Introductions
Orchestrator API Overview
Exploring the Swagger Interface
Test Manager API Highlights
Streamlining Automation & Testing with APIs (Demo)
Q&A and Open Discussion
Perfect for developers, testers, and automation enthusiasts!
👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/
This session streamed live on April 29, 2025, 18:00 CET.
Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.
Special Meetup Edition - TDX Bengaluru Meetup #52.pptx
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55 We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
Technology Trends in 2025: AI and Big Data Analytics
Technology Trends in 2025: AI and Big Data AnalyticsInData Labs At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including:
-Artificial Intelligence Market Overview
-Strategies for AI Adoption in 2025
-Anticipated drivers of AI adoption and transformative technologies
-Benefits of AI and Big data for your business
-Tips on how to prepare your business for innovation
-AI and data privacy: Strategies for securing data privacy in AI models, etc.
Download your free copy nowand implement the key findings to improve your business.
AI and Data Privacy in 2025: Global Trends
AI and Data Privacy in 2025: Global TrendsInData Labs In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy.
This infographic contains:
-AI and data privacy: Key findings
-Statistics on AI data privacy in the today’s world
-Tips on how to overcome data privacy challenges
-Benefits of AI data security investments.
Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.
Role of Data Annotation Services in AI-Powered Manufacturing
Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo From predictive maintenance to robotic automation, AI is driving the future of manufacturing. But without high-quality annotated data, even the smartest models fall short.
Discover how data annotation services are powering accuracy, safety, and efficiency in AI-driven manufacturing systems.
Precision in data labeling = Precision on the production floor.
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungen
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
Ad
DevOps in the Real World
- 1. DevOps in the Real World by Max Yermakhanov
- 2. • Max Yermakhanov • Senior Consultant at O# • Microsoft ALM MVP • Email: [email protected] • [email protected] • Twitter: @yermax
- 3. We’re not hear to talk about the DevOps unicorns
- 7. We’re here to talk about the real world companies
- 12. OK. Thanks, but how do I get there?
- 15. How do we get a better place
- 16. Let’s get terminology right first… What is DevOps?
- 18. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 19. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 20. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 21. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 22. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 23. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 24. People, processes and tools working together to enable continuous delivery of value to the end users fast(er)
- 27. Happy DevOps DEV OPS Production
- 30. Start simple
- 31. One codebase and compatible infrastructure
- 34. Separate configuration from code
- 37. One codebase • Set configuration at deployment time • Apply configuration at runtime • Automate your tests • Auto-provision your infrastructure as and when needed
- 38. Get your versioning right
- 39. Build once, deploy many
- 41. Start with the basics • One codebase • Separate configuration from code • Infrastructure as code • Build once, deploy many • Versioning • Measuring
- 42. Preparing your code for microservices
- 43. Make your deployments easy(ier)
- 44. Improve your cycle time
- 46. Remove the bottlenecks one at a time
- 47. Build and release pipeline
- 48. Stop the bad stuff from getting to production
- 49. Feature flags • Wrap your changes in flags • Configure externally • Deploy with feature flag turned off • Test in production?!? • Separate “Launch” from “Deploy”
- 50. Improve your cycle time • Automate deployments • Build a robust pipeline • Use feature flags
- 51. Culture shift
- 52. No more silos. We’re all in this together…
- 53. Use “task” teams
- 54. Faster feedback
- 56. Culture shift • No more silos • Faster feedback loops • Experimentation is good
- 58. Thank you