Matthew Skelton presented on common anti-patterns seen when adopting continuous delivery practices. The anti-patterns included not reading the Continuous Delivery book, having long and slow deployment pipelines, claiming continuous delivery is not suitable, lacking effective logging and metrics, insufficient investment in builds and deployments, neglecting operational aspects, forgetting about database management, attempting to "just plug in" a pipeline, and prematurely adopting containers before establishing good practices. Skelton recommended focusing on practices like using the Continuous Delivery book, shortening pipelines, logging and metrics, funding build/deployment, addressing all features, managing databases, rearchitecting for continuous delivery, and establishing practices before complexity.
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not measuring delays between value-add activities
- Ignoring Cost-of-Delay and job size
- Not funding the build/test/deployment capability properly
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Attendees will learn:
1. Why Continuous Delivery (CD) is useful for almost all modern software
2. How to approach CD for databases
3. How to make CD really 'fly' within the organisation
4. How to 'sell' CD to business stakeholders
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
How to break apart a monolithic system safely without destroying your team - talk at Velocity Eu Amsterdam on 7 Nov 2016
You'll learn some team-first heuristics to use when decomposing large or monolithic software into smaller pieces.
http://conferences.oreilly.com/velocity/devops-web-performance-eu/public/schedule/detail/52879
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Matthew Skelton is co-founder of Skelton Thatcher Consulting / @matthewpskelton
For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Talk given at DevOpsCon Munich 2016 - https://devopsconference.de/session/how-and-why-to-design-your-teams-for-modern-software-systems/
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not measuring delays between value-add activities
- Ignoring Cost-of-Delay and job size
- Not funding the build/test/deployment capability properly
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Attendees will learn:
1. Why Continuous Delivery (CD) is useful for almost all modern software
2. How to approach CD for databases
3. How to make CD really 'fly' within the organisation
4. How to 'sell' CD to business stakeholders
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
How to break apart a monolithic system safely without destroying your team - talk at Velocity Eu Amsterdam on 7 Nov 2016
You'll learn some team-first heuristics to use when decomposing large or monolithic software into smaller pieces.
http://conferences.oreilly.com/velocity/devops-web-performance-eu/public/schedule/detail/52879
How to break apart a monolithic system safely without destroying your team
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart?
By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Matthew Skelton is co-founder of Skelton Thatcher Consulting / @matthewpskelton
For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Talk given at DevOpsCon Munich 2016 - https://devopsconference.de/session/how-and-why-to-design-your-teams-for-modern-software-systems/
DevOps and All the Continuouses w/ Helen BealSonatype
DevOps promises to make better software faster and more safely and many organizations begin by practicing Continuous Integration and moving on to Continuous Delivery and sometimes even extending as far as Continuous Deployment - but this is only the tip of the iceberg.
DevOps demands a fundamental shift in the way we work and requires all participants in an organization to live its principles. It’s much more than a tool chain.
When you are delivering software in an Agile manner in fortnightly sprints, are you still funding in an annual manner? Are you adhering to The Third Way? I.e. are you practicing Continuous Experimentation? Continuous Learning? How are you doing Continuous Testing? Are you including security in that? Have you have Continuous Improvement in your organization for years? When does Continuous Everything turn into Continuous Apathy?
Advanced A/B Testing at Wix - Aviran Mordo and Sagy Rozman, Wix.comDevOpsDays Tel Aviv
While A/B test is a very known and familiar methodology for conducting experiments on production when you do that on a large scale it has many challenges in the organization level and operational level.
At Wix we are practicing continuous delivery for over 4 years. Conducting A/B tests and writing feature toggles is at the core of our development process. However when doing so on a large scale, with over 1000 experiments every month, it holds many challenges and affect everyone in the company, from developers, product managers, QA, marketing and management.
In this talk we will explain what is the lifecycle of an experiment, some of the challenges we faced and the effect on our development process.
* How an experiment begins its life
* How an experiment is defined
* How do you let non technical people control the experiment while preventing mistakes
* How an experiment go live, what is the lifecycle of an experiment from beginning to end
* What is the difference between client and server experiments
* How do you keep the user experience and not confuse them
* How does it affect the development process
* How can QA test an environment that changes every 9 minutes
* How can support help users when every user may be part of different experiment
* How can we find if an experiment is causing errors when you have millions of permutations [at least 2^(number of active experiments)]
* What are the effects of always having multiple experiments on system architecture
* What are the development patterns when working with AB test
At Wix we have developed our 3rd generation experiment system called PETRI, which is (will be) open sourced, that helps us maintain some order in a chaotic system that keep changing. We will also explain how PETRI works, what are the patterns in conducting experiments that will have a minimal effect on performance and user experience.
Devops at SlideShare: Talk at Devopsdays Bangalore 2011Kapil Mohan
Presentation for the talk at Devopsdays Bangalore 2011 (August 26th & 27th)
This is about why we embraced devops at SlideShare and our experiences, achievements and insights in adopting devops.
In this webinar we'll explore what is DevOps culture, why it's important, and how it differs from many typical organisational cultures and why. We'll see some simple things we can do to help nurture a DevOps culture within our organisations, and investigate some collaboration and team patterns which can help to change behaviour to encourage DevOps to flourish.
Walk This Way - An Introduction to DevOpsNathen Harvey
"DevOps" is a term that has become mainstream enough to be hated, misunderstood, misused, and abused. But what is "DevOps"? And, more importantly, why should I care?
Open Source and Content Management (+audio)Matt Hamilton
Open Source solutions are becoming more commonplace in corporate IT, with two thirds of companies using Open Source today or planning to use it soon. We've all heard the hype: cheaper to buy, cheaper to run, cheaper to fix. Using Open Source software reduces your risks. But how does this translate to the world of Content Management?
The advantages of Open Source systems go beyond simple cost savings. Content management by its very nature requires a significant level of customisation and integration to meet business requirements. By not prohibiting the inspection and modification of the source code, Open Source enables a level of flexibility not available with proprietary systems.
Open Source enables you to leverage a culture of trust and openness, rather than secrecy. By having access to the source code, a customer can be safe in the knowledge that everything that the software vendor was intended to deliver can be independently verified.
In this talk you will learn how the Open Source community works, how its distributed nature makes it more resilient, and how you can become a part of it and benefit. We will cover the key criteria to consider when evaluating which Open Source CMS is the right fit for your requirements.
DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery.
Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.
Software operability and run book collaboration - DevOps Summit, BangaloreMatthew Skelton
Making software work well in production (through good software operability) is one of the goals of DevOps. Collaboration between Dev and Ops on the 'run book' or operation manual is one way to open up communication channels between Dev and Ops, leading to improved software operability.
This is the slide deck I used at DevOps Summit, Bangalore, on 18th December 2013.
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown
Introduce DevOps to the uninitiated
Demystify the terminology and techno-centric jargon
Provide an assessment model that you can take back to your organization to help establish a baseline of behaviors and practices, and guidance on moving towards more of a DevOps culture
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated WorkflowBohyun Kim
A talk given at the 2017 ALA (American Library Association) Annual Conference, Chicago, June 25, 2017. Presenters: Bohyun Kim, Associate Director for Library Applications and Knowledge Systems, Brad Gerhart, Web Developer, Zak Burke, Senior Web Developer from
University of Maryland, Baltimore - Health Sciences and Human Services Library.
DevOps and All the Continuouses w/ Helen BealSonatype
DevOps promises to make better software faster and more safely and many organizations begin by practicing Continuous Integration and moving on to Continuous Delivery and sometimes even extending as far as Continuous Deployment - but this is only the tip of the iceberg.
DevOps demands a fundamental shift in the way we work and requires all participants in an organization to live its principles. It’s much more than a tool chain.
When you are delivering software in an Agile manner in fortnightly sprints, are you still funding in an annual manner? Are you adhering to The Third Way? I.e. are you practicing Continuous Experimentation? Continuous Learning? How are you doing Continuous Testing? Are you including security in that? Have you have Continuous Improvement in your organization for years? When does Continuous Everything turn into Continuous Apathy?
Advanced A/B Testing at Wix - Aviran Mordo and Sagy Rozman, Wix.comDevOpsDays Tel Aviv
While A/B test is a very known and familiar methodology for conducting experiments on production when you do that on a large scale it has many challenges in the organization level and operational level.
At Wix we are practicing continuous delivery for over 4 years. Conducting A/B tests and writing feature toggles is at the core of our development process. However when doing so on a large scale, with over 1000 experiments every month, it holds many challenges and affect everyone in the company, from developers, product managers, QA, marketing and management.
In this talk we will explain what is the lifecycle of an experiment, some of the challenges we faced and the effect on our development process.
* How an experiment begins its life
* How an experiment is defined
* How do you let non technical people control the experiment while preventing mistakes
* How an experiment go live, what is the lifecycle of an experiment from beginning to end
* What is the difference between client and server experiments
* How do you keep the user experience and not confuse them
* How does it affect the development process
* How can QA test an environment that changes every 9 minutes
* How can support help users when every user may be part of different experiment
* How can we find if an experiment is causing errors when you have millions of permutations [at least 2^(number of active experiments)]
* What are the effects of always having multiple experiments on system architecture
* What are the development patterns when working with AB test
At Wix we have developed our 3rd generation experiment system called PETRI, which is (will be) open sourced, that helps us maintain some order in a chaotic system that keep changing. We will also explain how PETRI works, what are the patterns in conducting experiments that will have a minimal effect on performance and user experience.
Devops at SlideShare: Talk at Devopsdays Bangalore 2011Kapil Mohan
Presentation for the talk at Devopsdays Bangalore 2011 (August 26th & 27th)
This is about why we embraced devops at SlideShare and our experiences, achievements and insights in adopting devops.
In this webinar we'll explore what is DevOps culture, why it's important, and how it differs from many typical organisational cultures and why. We'll see some simple things we can do to help nurture a DevOps culture within our organisations, and investigate some collaboration and team patterns which can help to change behaviour to encourage DevOps to flourish.
Walk This Way - An Introduction to DevOpsNathen Harvey
"DevOps" is a term that has become mainstream enough to be hated, misunderstood, misused, and abused. But what is "DevOps"? And, more importantly, why should I care?
Open Source and Content Management (+audio)Matt Hamilton
Open Source solutions are becoming more commonplace in corporate IT, with two thirds of companies using Open Source today or planning to use it soon. We've all heard the hype: cheaper to buy, cheaper to run, cheaper to fix. Using Open Source software reduces your risks. But how does this translate to the world of Content Management?
The advantages of Open Source systems go beyond simple cost savings. Content management by its very nature requires a significant level of customisation and integration to meet business requirements. By not prohibiting the inspection and modification of the source code, Open Source enables a level of flexibility not available with proprietary systems.
Open Source enables you to leverage a culture of trust and openness, rather than secrecy. By having access to the source code, a customer can be safe in the knowledge that everything that the software vendor was intended to deliver can be independently verified.
In this talk you will learn how the Open Source community works, how its distributed nature makes it more resilient, and how you can become a part of it and benefit. We will cover the key criteria to consider when evaluating which Open Source CMS is the right fit for your requirements.
DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery.
Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.
Software operability and run book collaboration - DevOps Summit, BangaloreMatthew Skelton
Making software work well in production (through good software operability) is one of the goals of DevOps. Collaboration between Dev and Ops on the 'run book' or operation manual is one way to open up communication channels between Dev and Ops, leading to improved software operability.
This is the slide deck I used at DevOps Summit, Bangalore, on 18th December 2013.
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown
Introduce DevOps to the uninitiated
Demystify the terminology and techno-centric jargon
Provide an assessment model that you can take back to your organization to help establish a baseline of behaviors and practices, and guidance on moving towards more of a DevOps culture
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated WorkflowBohyun Kim
A talk given at the 2017 ALA (American Library Association) Annual Conference, Chicago, June 25, 2017. Presenters: Bohyun Kim, Associate Director for Library Applications and Knowledge Systems, Brad Gerhart, Web Developer, Zak Burke, Senior Web Developer from
University of Maryland, Baltimore - Health Sciences and Human Services Library.
This talk provides an introduction to the OpenStack Interop Working Group, what it does, and how it works. We'll also look into some upcoming new work, such as the development of vertical programs (e.g. for clouds being built for NFV or other specific use cases).
Innovate Better Through Machine data AnalyticsHal Rottenberg
This talk was presented at IP Expo Manchester in May, 2016. the themes discussed are:
- how does machine data relate to devops?
- how can tracking this data lead to better outcomes?
- what types of data are important to track?
Creating a DevOps Practice for Analytics -- Strata Data, September 28, 2017Caserta
Over the past eight or nine years, applying DevOps practices to various areas of technology within business has grown in popularity and produced demonstrable results. These principles are particularly fruitful when applied to a data analytics environment. Bob Eilbacher explains how to implement a strong DevOps practice for data analysis, starting with the necessary cultural changes that must be made at the executive level and ending with an overview of potential DevOps toolchains. Bob also outlines why DevOps and disruption management go hand in hand.
Topics include:
- The benefits of a DevOps approach, with an emphasis on improving quality and efficiency of data analytics
- Why the push for a DevOps practice needs to come from the C-suite and how it can be integrated into all levels of business
- An overview of the best tools for developers, data analysts, and everyone in between, based on the business’s existing data ecosystem
- The challenges that come with transforming into an analytics-driven company and how to overcome them
- Practical use cases from Caserta clients
This presentation was originally given by Bob at the 2017 Strata Data Conference in New York City.
Achieving continuous testing is a daunting task for many test teams still struggling with combining agile, test automation, and increased speed. We know that change is rarely easy. Fixing or getting rid of some practices is tough. However, one-step-at-a-time change can take you far and fast. To jumpstart your team, Michael Hackett shares learnings from four LogiGear clients in various stages of continuous integration, continuous testing, and continuous delivery. Failures in one organization ranged from naively thinking that automating every manual script was a good thing to misusing agile principles; this team needed an overhaul. Michael began with better test design, got rid of old style automation, and defined four sets of automated suites for different purposes, environments, and execution times. Very quickly the test team was contributing faster and providing more useful feedback to the whole development team. Join Michael and get moving to higher levels of continuous testing.
Slides from this webcast: bit.ly/mTUTq4
Discussion of what DevOps is, why we need it, what sorts of shared tooling helps it, and how it fits in to an enterprise rollout.
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.
OGh Oracle Fusion Middleware Experience 2016 bij FIGI Zeist
Door Maarten Smeets and Robbrecht van Amerongen, 16-02-2016
Ogh fmw experience 16 februari 2016
How the DevOps company-wide initiative affected the development team in the Bakson, Serbia (a part of Ticketmaster's engineering team). And what tooling were used to automate QA processes.
Presentation was created for DevOps meetup in Belgrade, on 11th October 2016. https://www.facebook.com/SevenBridgesGenomics/photos/?tab=album&album_id=1338738752836488
Covering topics like:
CI CD DevOps Jenkins TFS TeamCity Compile Test Package Delpoy
See Disclaimer in the last slide and/or in file comments, if available.
Similar to Continuous Delivery antipatterns from the wild - Matthew Skelton - IPEXPO Manchester 2016 (20)
In this talk, Matthew Skelton (Skelton Thatcher Consulting) explores five practical, tried-and-tested, real-world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT.
Logging as a live diagnostics vector with sparse event IDs
Operational checklists and 'run book dialogue sheets' as a discovery mechanism for teams
Endpoint healthchecks as a way to assess runtime dependencies and complexity
Correlation IDs beyond simple HTTP calls
Lightweight 'User Personas' as drivers for operational dashboards
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or 'serverless' case. However, the principles - logging as a live diagnostics vector, event IDs for discovery, etc - work remarkably well across very different technologies.
From a talk at Agile in the City Bristol 2017 http://agileinthecity.net/2017/bristol/sessions/index.php?session=44
Modern software systems now increasingly span cloud and on-premises deployments and remote embedded devices and sensors. These distributed systems bring challenges with data, connectivity, performance, and systems management; to ensure success, you must design and build with operability as a first-class property.
Matthew Skelton shares five practical, tried-and-tested techniques for improving operability with many kinds of software systems, including the cloud, serverless, on-premises, and the IoT: logging as a live diagnostics vector with sparse event IDs; operational checklists and runbook dialog sheets as a discovery mechanism for teams; endpoint health checks as a way to assess runtime dependencies and complexity; correlation IDs beyond simple HTTP calls; and lightweight user personas as drivers for operational dashboards.
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generating and shipping of logs and metrics looks very different from cloud or serverless cases. However, the principles—logging as a live diagnostics vector, event IDs for discovery, etc.—work remarkably well across very different technologies.
Drawing from his experience helping teams improve the operability of their software systems, Matthew explains what works (and what doesn’t) and how teams can expand their understanding and awareness of operability through these straightforward, team-friendly techniques.
From a talk given by Matthew Skelton at Velocity Conference EU 2017 - https://conferences.oreilly.com/velocity/vl-eu/public/schedule/detail/61954
Modern software systems now increasingly span cloud, on-premise, and remote embedded devices & sensors. These distributed systems bring challenges with data, connectivity, performance, and systems management, so for business success we need to design and build with operability as a first class property.
In this talk, we explore five practical, tried-and-tested, real world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT:
- Logging as a live diagnostics vector with sparse Event IDs
- Operational checklists and 'Run Book dialogue sheets' as a discovery mechanism for teams
- Endpoint healthchecks as a way to assess runtime dependencies and complexity
- Correlation IDs beyond simple HTTP calls
- Lightweight 'User Personas' as drivers for operational dashboards
These techniques work very differently with different technologies. For instance, an IoT device has limited storage, processing, and I/O, so generation and shipping of logs and metrics looks very different from the cloud or Serverless case. However, the principles - logging as a live diagnostics vector, Event IDs for discovery, etc. - work remarkably well across very different technologies.
Presenters: Matthew Skelton and Rob Thatcher, Skelton Thatcher Consulting
Webinar: Operability is all about making software work well in Production. In this webinar, we explore practical, tried-and-tested, real world techniques for improving operability with many kinds of software systems, including cloud, Serverless, on-premise, and IoT: logging with Event IDs, Run Book dialogue sheets, endpoint healthchecks, correlation IDs, and lightweight User Personas.
Target audience: Software Developer, Tester, Software Architect, DevOps Engineer, Delivery Manager, Head of Delivery, Head of IT.
Benefits: Attendees will gain insights into operability and why this is important for modern software systems, along with practical experience of techniques to enhance operability in almost any software system they encounter.
Moving from a monolith to microservices can be daunting. How do we choose the right bounded contexts? How small should services be? Which teams should get which services? And how do we keep things from falling apart? By starting with the needs of the team, we can infer some useful heuristics for evolving from a monolithic architecture to a set of more loosely coupled services.
Talk given at London DevOps meetup group - June 2017 - https://www.meetup.com/London-DevOps/events/238827763/
For effective, modern, Cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
A talk given at JAX DevOps London - April 2017
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
In summary, this talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible.
Takeaways:
• The implications of Conway’s Law for software teams
• Cognitive Load for teams
• Effective team topologies
• Team evolution
Tools like GoCD and TeamCity are excellent components of advanced Continuous Delivery deployment systems. They help us focus on deployment pipelines and the flow of changes, rather than "builds" or "environments". We can further enhance these tools by using frameworks like Rancher to manage GoCD and TeamCity as highly available, always-on deployment services. In this talk, we'll see how to use Rancher to run deployment pipeline tooling like GoCD and TeamCity, and how this lets us focus on the important parts of Continuous Delivery: getting changes to Production safely and rapidly.
Modern log aggregation & search tools provide significant new capabilities for teams building, testing, and running software systems. By treating logging as a core system component, and using techniques such as unique event IDs, transaction tracing, and structured log output, we gain rich insights into application behaviour and health. This talk explains why it is valuable to test aspects of logging and how to do this with modern log aggregation tooling.
Forget the gap between Dev and Ops - the gap between Devs and DBAs is a chasm. Here are some observations from the field about the causes of the rift and some ideas about how to close the gap (and even whether the gap is worth closing). Oh, and I'm writing a book about it.
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.
Traceability, deployability, recoverability, diagnosability, monitorability, and high quality logging are key features of a software system, along with user-visible features surfaced via the UI, or a capability of an API endpoint.
However, many Product Owners understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.
This session brings Scrum Masters and Product Owners up to speed on operational features and covers proven practices for improving operability in an Agile context, empowering Product Owners to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
How do team topologies influence a DevOps culture? In this talk, we explore different kinds of organisational structures - some good for DevOps, some bad - and see how they affect the kind of collaboration and interaction between teams. Warning: hats are also involved.
Talk at TechUG day in Leeds on 22nd October 2015
The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.
Deployability, recoverability, diagnosability, monitorability, and high quality logging are simply features of a software system, along with user-visible features surfaced via the UI, or a capability of an API endpoint.
However, many Product Managers understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.
This session aims to bring Scrum Masters and Product Owners up to speed on operational features, empowering them to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.
What team configuration is right for DevOps to work? Devs doing Ops? Ops doing Dev? Everyone doing a bit of everything, or a special new silo doing Docker and Jenkins in the corner of the room?
In this talk, Matthew Skelton and Rob Thatcher joins speculation with practical in-the-trenches experience to arrive at some working 'team topologies' for effective DevOps.
Also involves audience participation. And hats :)
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.
However, many Product Managers understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.
This session aims to bring Scrum Masters and Product Owners up to speed on operational features, empowering them to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
To many people ITIL seems like the antithesis of Agile, with process-heavy, manual checks and approval gates a blocker to rapid delivery. However, at its core ITIL recommends iterative and continual improvement of software services based on the ‘Plan, Do, Check, Act’ (PDCA) cycle of Deming, an approach also central to DevOps. In this talk we’ll explore how – if implemented appropriately – ITIL and Agile can complement each other for a DevOps approach to iterative evolution of successful software systems.
From our talk at Unicom DevOps Summit on 26th March 2015 in London.
Presentation given at QCon London on 4th March 2015
Tools, Collaboration, and Conway's Law: how to choose and use tools effectively for Continuous Delivery and DevOps
With an ever-increasing array of tools and technologies claiming to 'enable DevOps' or 'implement Continuous Delivery', how do we know which tools to try or to choose? In-house, open source, or commercial? Ruby or shell? Dedicated or plugins? It transpires that highly collaborative practices such as DevOps and Continuous Delivery require new ways of assessing tools and technologies in order to avoid creating new silos.
Matthew Skelton shares his recent experience of helping many different organisations to evaluate and select tools to facilitate DevOps and Continuous Delivery, including version control, log aggregation, deployment pipelines, monitoring and metrics, and infrastructure automation tools; the recommendations may surprise you.
As a Developer, you cannot attach the debugger to your application in Production, but you *can* use logging in a way which means you can diagnose problems very easily in both development AND Production. You also get to make friends with Operations people - win! In this tutorial, we'll show you how to get up and running with ELK (Elastic Search, LogStash, Kibana) with Vagrant on your developer machine for awesome logging-fu. Warning: may contain DevOps.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdfJay Das
With the advent of artificial intelligence or AI tools, project management processes are undergoing a transformative shift. By using tools like ChatGPT, and Bard organizations can empower their leaders and managers to plan, execute, and monitor projects more effectively.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
12. Keep Everything in Version Control
Done Means Released
Don’t Check In on a Broken Build
Never Go Home on a Broken Build
Fail the Build for Slow Tests
Only Build Your Binaries Once
Deploy the Same Way to Every Environment
25. “Nope.
CD is fine for some
systems/teams/software,
but each company should
make their own business
decisions about how often
to release code.”
(Why every development team needs
continuous delivery)
26. “…each company should make their own business
decisions about how often to release code…”
err, this is exactly what we get with
Continuous Delivery practices!
72. Not reading any of ‘Continuous Delivery’ book
Long and slow deployment pipelines
“Continuous Delivery is not for us”
No effective logging or application metrics
No investment in build & deployment
Operational aspects not addressed well
Forgetting the database
“Just plug in a deployment pipeline”
Container envy
73. Use the CD book
Short, wide pipelines
Deliver to a simulation environment
Aggregated logging + metrics
Explicitly fund build & deployment
Single backlog for all features
Use a tool for DB changes + version control
Re-architect for Continuous Delivery
Adopt good practices before using containers
75. References
‘Continuous Delivery’ by Jez Humble & Dave Farley, 2010
https://www.amazon.co.uk/Continuous-Delivery-Deployment-Automation-Addison-
Wesley/dp/0321601912/
‘Deployment Pipeline anti-patterns’ by Jez Humble
http://continuousdelivery.com/2010/09/deployment-pipeline-anti-patterns/
‘Why every development team needs continuous delivery’ by Sarah Goff-Dupont [Atlassian]
http://blogs.atlassian.com/2015/10/why-continuous-delivery-for-every-development-team/
‘Continuous Delivery with Windows and .NET’ by Chris O’Dell & Matthew Skelton, O’Reilly, 2016
http://cdwithwindows.net/
‘Database Lifecycle Management’ by Grant Fritchey and Matthew Skelton, Redgate, 2016
http://thedlmbook.com/