Continuous Delivery
Showing 24 out of 24 results
Continuous Delivery, Microservices & Serverless in 10 Minutes
Continuous delivery has been around for more than 15 years, but it’s only gained wider adoption in recent years. In this Unscripted interview, Nicki Watt and Ken Mugrage chat with Preben Thoro about the evolution of CD and how it ties in with recent developments in the software architecture space. Find out when you should use CD along with its connection to microservices, serverless, machine learning and graph theory.
Expert Talk: DevOps & Software Architecture
As software architecture continues to evolve rapidly, we are constantly confronted with new challenges. Simon Brown, Dave Farley and Hannes Lowette cover some of the recent trends in software architecture touching on terms such as DevOps and how to deal with complexity. They also reference concepts that have stirred debates forever and are still not done right, like bounded context and continuous delivery.
The Art of Unit Testing
How can you leverage unit testing and test-driven development to create better software. Find out from Roy Osherove, the author of “The Art of Unit Testing,” and Dave Farley, the co-author of “Continuous Delivery”, what are some of the main considerations to be made before starting the design and why that is important.
Architecting for Scale
Ready to scale your company or are you working for a company that is in the process of scaling up? Find out how you can build your software architecture or what changes you need to do to your current one so your product doesn’t break. Join Lee Atchinson and Ken Gavranovic to learn what are some best practices around architecting and operating for scale: risk management, moving to microservices, continuous vs future releases.
Software Engineering at Google
What’s the difference between programming and software engineering? Join Titus Winters, co-curator of “Software Engineering at Google”, and Matt Kulukundis while they approach the lessons learned by software engineering teams at Google in establishing the right practices for writing sustainable code in a safe environment. Discover what Google is still trying to improve on and what software decisions are difficult to undo.
Software Architecture: The Hard Parts
There are no easy decisions in software architecture. Instead, there are many hard parts--difficult problems or issues with no best practices--that force you to choose among various compromises. With this book, you'll learn how to think critically about the trade-offs involved with distributed architectures.
Farley's Laws
We are not as smart as we think we are. Even us software developers!! What we think of as reality isn't. When we think we are being rational, we are not. When we listen to experts and trust in their wisdom, we are fooling ourselves. Meanwhile, software development is one of the more complex tasks that we mere mortals undertake. So what does it really take to overcome the limitations of our biology? How do we overcome our desire to jump to conclusions and guess at solutions? This mildly humorous, entertaining talk explores some of the fallibilities inherent in our biology and addresses what it takes to solve genuinely complex problems in the face of our propensity to make wild guesses? To put it another way, what do you need to understand to completely grasp how agile, lean development, DevOps and Continuous Delivery really work?
Acceptance Testing for Continuous Delivery
Writing and maintaining a suite acceptance tests that can give you a high level of confidence in the behaviour and configuration of your system is a complex task. In this talk Dave will describe approaches to acceptance testing that allow teams to: work quickly and effectively; build excellent functional coverage for complex enterprise-scale systems; manage and maintain those tests in the face of change, and of evolution in both the codebase and the understanding of the business problem. This talk will answer the following questions, and more: How do you fail fast? How do you make your testing scalable? How do you isolate test cases from one-another? How do you maintain a working body of tests when you radically change the interface to your system?
It’s Not Continuous Delivery If You Can’t Deploy Right Now
I hear people say all the time that they're practicing continuous delivery. This declaration is often followed by something like, "I can let the security team know anytime", or "I just have to run the performance tests". If you can't push your software to production right now, you're not done with your continuous delivery journey. In this talk, we’ll go over code management strategies, deployment patterns and types of continuous delivery pipelines you can use to make sure you can “deploy right now”.
Building a Metrics Optimised Pipeline (Full Automation)
Pretty much every development team is looking for ways to deliver code faster and better. Getting the basics of a Continuous Delivery pipeline in place is pretty easy, and in a cloud-native, microservice environment, testing and validating *individual* services should become simpler, too. However, ensuring that an *entire* set of microservices performs well together is much more challenging, especially if we want to go beyond *functional* testing. Migrating to a microservice architecture can also have significant implications on the scalability and performance of your applications. Andrew will describe ways in which we can incorporate testing and metrics into our Continuous Delivery pipelines that can help us detect potential performance and scalability problems early. He'll also discuss how we can use some of the same tooling to go beyond monitoring technical attributes of our production systems, and start examining whether we're actually making things better for our users.
Software Engineering - Development in 100 Years Time
Join this session on continuous delivery with our all-time favorite returning speaker Dave Farley. **If we were to more clearly define our discipline what would that look like? If “Software Engineering” is real “Engineering” then wouldn't we expect the principles to be long-lasting, durable and probably unsurprising?** Dave Farley will answer difficult questions like, what sort of ideas will be as true of “Software Engineering” in 100 years as they are today? What are the foundations on which we could begin to build a true Engineering discipline for our profession? This talk with Dave explores some of those ideas and describes why Continuous Delivery may be the best starting point that we have for that. **In this talk, you'll learn:** * About software engineering now and in 100 years * How Continuous Delivery could be the starting point of true Engineering discipline
Mobile Continuous Delivery is closer, easier (and more fun) than you think!
Mobile Maturity is Low! By now, most companies have accepted the benefits of continuous delivery in web applications, but, interestingly, fail to apply the same principles when it comes to mobile app development. Why? Because it's hard. However, the times are a-changing', to quote a recent Nobel Prize winner. A second generation of tools and cloud services have recently become available and the barrier of entry is much low lower than most teams believe. In this talk, we discuss the benefits of continuous delivery when applied to mobile, but also challenges unique to mobile. We show, using live demos, how easy it is to get started and provide value early on in a project. This is accessible for everyone from Indie developers, to Start-ups to Enterprises. We conclude with practical tips from engineering teams, who have been doing this for years now.
With Age Comes Wisdom (Hopefully): Lessons Learned in 15 Years of Building Software
Key topics include: - The need for defining and sharing a business and technical vision - Developing software begins with models, both mental (shared) models, and modelling the real world - Benefits of codifying requirements and automating assertions within a continuous delivery pipeline - Using dashboards and communication hacks in order to increase feedback and communication
Modern Continuous Delivery
The first product build specifically for Continuous Delivery pipelines came out over 10 years ago. The Continuous Delivery book came out 9 years ago. In the time since we’ve seen massive changes in the types of software we’re building, testing and deploying. Yet the way we think about pipelines hasn’t changed in many cases. Now that we as an industry are trying to think “cloud first” what changes does that imply in our architecture? What about our organization? How we test? How we secure our systems? This talk will show several intertwined changes to how we think about pipelines to support the other changes in our industry.
Deliver Results, Not Just Releases: Control & Observability in CD
How do companies like Netflix, LinkedIn, and booking.com crush it year after year? Yes, they release early and often. But they also build control and observability into their CD pipeline to turn releases into results. Progressive delivery and the statistical observation of real users (sometimes known as “shift right testing” or “feature experimentation”) are essential CD practices. They free teams to move fast, control risk and focus engineering cycles on work that delivers results, not just releases. Learn implementation strategies and best practices for adding control and observability to your CD pipeline: Where should you implement progressive delivery controls: front-end or back-end? Why balancing centralization/consistency and local team autonomy in your implementation will increase the odds of achieving results you can trust and observations your teams will act upon. What two pieces of data make it possible to attribute system and user behavior changes to any deployment? How “guardrail” metrics can automate observability of unintended consequences of deployments, without adding overhead to teams making changes or tasking your exploratory testers and data scientists to go looking for them. This talk is from our partner
Testing in Production
How do you know your feature is working perfectly in production? If something breaks in production, how will you know? Will you wait for a user to report it to you? What do you do when your staging test results do not reflect current production behavior? If you want to test proactively as opposed to reactively, try testing in production!<br> **By testing in production, you have increased accuracy of test results, your tests will run faster due to the elimination of mocks and bad data, and you will have higher confidence before releases.** <br> You can accomplish this through feature flagging, continuous delivery, and data cleanup. Only when your end-to-end tests pass in production will you know that your features are truly working. After this session Talia Nassi will leave you with strategies to mitigate risk, to better your understanding of the steps to get there, and to shift your company’s testing culture, so you can provide the best possible experience to your users.<br> **In this talk, you'll learn:**<br> * You will learn how to safely test your code in production * You'll learn how to use feature flagging * How to mitigate risks of testing in production * You'll learn how to shift your company’s testing culture
Modern Continuous Delivery
The first product build specifically for Continuous Delivery pipelines came out over 10 years ago. The Continuous Delivery book came out 9 years ago. In the time since we’ve seen massive changes in the types of software we’re building, testing and deploying. Yet the way we think about pipelines hasn’t changed in many cases. Now that we as an industry are trying to think “cloud first” what changes does that imply in our architecture? What about our organization? How we test? How we secure our systems? This talk will show several intertwined changes to how we think about pipelines to support the other changes in our industry.
Software Engineering - Development in 100 Years Time
Join this session on continuous delivery with our all-time favorite returning speaker Dave Farley. **If we were to more clearly define our discipline what would that look like? If “Software Engineering” is real “Engineering” then wouldn't we expect the principles to be long-lasting, durable and probably unsurprising?** Dave Farley will answer difficult questions like, what sort of ideas will be as true of “Software Engineering” in 100 years as they are today? What are the foundations on which we could begin to build a true Engineering discipline for our profession? This talk with Dave explores some of those ideas and describes why Continuous Delivery may be the best starting point that we have for that. **In this talk, you'll learn:** * About software engineering now and in 100 years * How Continuous Delivery could be the starting point of true Engineering discipline
Progressive Delivery: Patterns & Benefits of Decoupling Deploy from Release
Progressive delivery allows you to switch from high-stakes “big bang” releases to the gradual exposure of code changes in production. The goal is to observe changes in the health of your systems and user behavior before ramping up to your entire user population. Early adopters of CD invented their own progressive delivery tooling and practices, freeing up their teams to move fast, limit the blast radius of issues found in production and focus engineering cycles on work that delivers more impact, not just more releases. What can we learn from the ways these pioneers of progressive delivery implemented gradual release mechanisms and automated repeatable and trustworthy reporting of KPIs? **In this fast-pace talk, Channing and Dave will introduce some ideas and look at specific examples of what we can learn from early adopters of progressive delivery. They will sum up what you've seen by documenting the patterns in checklists you can take away to establish or extend these proven patterns in your own environment.** **In this talk, you'll learn:**<br> * A concise & sharable definition of progressive delivery * Benefits of progressive delivery you can point to guide and promote your implementation * Challenges overcome by early pioneers (so you can avoid re-learning the same lessons the hard way) * Essential foundation capabilities and implementation patterns you can adapt to your environment (shared as a checklist you can take back with you)
Testing in Production
How do you know your feature is working perfectly in production? If something breaks in production, how will you know? Will you wait for a user to report it to you? What do you do when your staging test results do not reflect current production behavior? If you want to test proactively as opposed to reactively, try testing in production!<br> **By testing in production, you have increased accuracy of test results, your tests will run faster due to the elimination of mocks and bad data, and you will have higher confidence before releases.** <br> You can accomplish this through feature flagging, continuous delivery, and data cleanup. Only when your end-to-end tests pass in production will you know that your features are truly working. After this session Talia Nassi will leave you with strategies to mitigate risk, to better your understanding of the steps to get there, and to shift your company’s testing culture, so you can provide the best possible experience to your users.<br> **In this talk, you'll learn:**<br> * You will learn how to safely test your code in production * You'll learn how to use feature flagging * How to mitigate risks of testing in production * You'll learn how to shift your company’s testing culture
Journey From 100’s of Pipelines To a Single Pipeline
Join Bhavik in this insightful session as he shares Capital One's journey towards a unified pipeline ecosystem, showcasing the power of DevOps in standardizing software delivery at scale. This presentation is ideal for engineers, leaders, architects, product managers, and business leaders who wish to harness DevOps to standardize their own software delivery life cycle. In this talk, Bhavik will discuss how Capital One: * Transitioned from the traditional "Somebody builds, somebody operates" approach to a modern, collaborative "You Build You Own" model. * Set an ambitious goal to unify software delivery tools and processes in order to accelerate their technology transformation. * Integrated various processes into a centralized pipeline system, creating a seamless software delivery experience. * Revolutionized the way they build software, fostering innovation and efficiency. * Empowered developers to rapidly build and deploy software while maintaining high standards of security, reliability, and quality. Discover how the pipeline ecosystem built at Capital One is leveraged by engineers across the company to build and deploy code, as well as to provision their infrastructure. Learn how your organization can benefit from adopting a similar approach and embrace the power of DevOps.
Automatic Testing Meets the Real World
"We are already agile, now can you please automate the test process, and make our company practice Continuous Delivery”… Sounds easy right? But what about the large legacy code base that is not designed for automated tests? What if our software is not a nice collection of microservices? How do you test a complex CAD/CAM GUI? Can we shape the culture of the company to make automated testing a cool thing for 300+ developers and testers? What is the cost, and do we even know the right approach to get a return on our investment? Can we use the results to document our medical software? These and more questions will be answered truthfully in this description of 3Shape’s transition towards automated tests in our build pipeline. The results of our pilot project, the strategy for rolling out to entire R&D department, the tools we used, and what did and did not work.
Transforming Legacy Applications in the Enterprise: Société Générale's Story
Share the continuity of Société Générale's journey with Docker Enterprise from different points of view, from executives to devops, with CD platform as an enabler. Creating a Dockerfile that runs a container on a developer's laptop is pretty straightforward. But extending that to stacks of containers running on a dozen environments (development, integration, testing, staging, production, etc.) with different configuration and topologies can be a challenge. This talk will cover aspects of our journey to Docker Enterprise: * What configuration should go in an image? * Where to put different types of configuration? Images, environment variables, entrypoint, ...? * How to store assets for building images and configuration for deployment in version control. We will discuss how Société Générale has implemented these, and what we plan next for Docker Enterprise deployment.
