Golang Weekly Newsletter, Gopa. Curated Golang news, tutorials, tools and more! 

Join thousands of other readers, 100% free, unsubscribe anytime.

Virtual environments are invaluable tools for developers be they data scientists, software/cloud/DevOps engineers and system administrators. They provide you with quick disposable environments for experimentation, testing and endless fresh starts.

Building a modern application often involves building it as a microservice, which provides developers with more flexibility and agility in terms of deployment options.

If you Google testing types in software engineering, you’ll certainly end with a list of hundreds of tests. We are sure not all of them will be useful for you. There are also some testing types that have two or three names and some others are very similar even if they have different names.

This article discusses the best practices that boost your CI/CD performance and how each impacts your software development journey.

What is a canary release?

The canary release concept comes from the 1920s coal mining industry. Back then, miners would carry caged canaries to help test the oxygen levels in the mines. If the canary died, it was a sign that there was too much carbon monoxide and they would leave the mine immediately.

In today’s world, a canary release is used to test the performance of the new application version in real-world usage. If there are bugs, then the new version is rolled back and the issues are fixed before another release. If there are no bugs and it works as expected, then it is scaled up until it replaces the old version completely. All this is made possible by the ability to control users’ traffic.