DevOps and modern web development is all about the shift towards continuous deployment. Integrating rapid and proactive testing can help make more deployments with confidence. In this session we look at the benefits of setting up smoke testing suites and get hands on creating automated tests.

• Proactive monitoring
• Smoke Testing - what, when and how
• Use Cases and scenarios: Availability, Functionality, Performance
• Test types
• End to End automated solutions (Synthetics): Ping, Simple Browser, Scripted Browser, API Test
• SLA’s and Reporting on your Monitors

No prior knowledge necessary

Prerequisites for the practical exercises: New Relic account (free): https://newrelic.com/signup

‍

Teams often find the concept of Continuous Deployment both mythical and terrifying.

Thanks to the State of DevOps reports, we can challenge the mythos that Continuous Deployment is only for unicorns and startups, but how do we tackle the fear?

The fear fundamentally stems from the unknown, and if we can show the team how to think about the problem, the team will solve it themselves.

As part of my consultancy, I leverage value stream mapping as a core practice for empowering teams with a self-reflective lens. The fundamental ability to see how they work.

Through this, I have seen teams make enduring progress towards becoming elite, challenge embedded assumptions, and see the fear morph into passion.

You'll learn

- How to run lightweight value stream mapping workshops

- How to use the DORA metrics for goal setting to drive improvements

- Common challenges and how to break through

Ackee is a leading company in developing frontend and mobile apps. Although they are created using different technologies, they need to be deployed via all available CI/CD pipelines for every developer in the company. Since there are always some minor issues, the DevOps goal is to receive as less support tickets as possible.

As a small team of three engineers, we had to learn the hard way. When the GAME OF HOARDS (of developers) started, we had to find the way to keep track, be in control, improvise, create and repeat (besides being angry and frustrated). Not to mention that we decided to leave our old codebase for Jenkins behind ....

You probably think - is there light at the end of this long, dark tunnel? OF COURSE, IT IS!

Join us when we introduce to you our specific approach to iOS, Android and web frontend GitLab CI pipelines which made our lives and work easier.

Infrastructure as Code (IaC) is a best practice, but with most infrastructure automation frameworks out there, we are actually writing configuration files, not real code. Is there another way? Can we finally get rid of tons and tons of YAML and JSON files? Yes! In this session, we’ll dive into the open-source Cloud Development Kit (CDK) that lets us define cloud infrastructure and Kubernetes apps in familiar programming languages like Python, Java, C#, TypeScript and JavaScript. Moreover, we look at CDK’s powerful constructs, which are high-level abstractions that bundle multiple services into ready-to-use architectures. After this session, you know how CDK works, what infrastructure you can automate with it (spoiler: almost anything) and how you could use it in your next project. Now, you can impress your colleagues by building complex architectures with just a few lines of code.

Unlike CI/CD pipelines for applications, we can't just delete the database and pop up a new one with each new version. Let's start with the production database, and get SQL Server content to developers in containers, and then flow schema and lookup data back into production with migration tools. You can bring the reliability and automation of CI/CD pipelines to Database DevOps with containers.

I'll tell a story on how we've hunted down a Heisenbug in a system that should have prevented it by design in the very first place and finally fixed it. The story involves Kafka, Kafka Connect, Elasticsearch, optimistic concurrency control, data inconsistencies, and SRE with plenty of good intentions that in a series of unfortunate circumstances caused a nasty bug.