In today’s post, we’ll dive into how we, at AppSignal, solved a daunting engineering challenge. Giving you a look into the kitchen, this post will show you how we tested a new database in production without having to worry about errors/downtime. Alright, let’s get cooking!
It can be really exciting when your development team is growing fast! But then you soon realize that managing all the developer tools to constantly create new projects or add users is becoming a full-time job. Well, not anymore. At least, not for Rollbar. We’re releasing our HashiCorp Terraform Verified Provider for Rollbar today, built in partnership with HashiCorp.
Imagine, you are developing Java software and suddenly you encounter an error? Where could you have possibly gone wrong? There are many types of errors that you will encounter while developing Java software, but most are avoidable. Some errors are minor lapses when writing codes but that is very much mendable. If you have an error monitoring tool such as Stackify Retrace, you can write codes with ease.
Setting up a proper monitoring overview over your application’s performance is a complex task. Normally, you’d first need to figure out what you need to monitor, then instrument your code, and finally make sense of all the data that has been emitted. However, with a few things set in place, and an APM that natively supports Ruby, it’s easier than ever to take this step. In this post, we’ll show you how you can do it too.
In the latest episode of our podcast, we talked to Russell Stephens from Compass about building mobile infrastructure, the evolution from self-hosted Jenkins to the cloud, and streamlining CI processes.
Jenkins is the world’s most popular CI/CD software, but — for a number of reasons — sees teams increasingly switch to cloud CI. What happens to all those Jenkins experts when teams
By now you've heard that Atlassian is deprecating its server products. For Jira users who cannot or do not want to move to the Cloud, this is troubling news. Data Center is an option, but it's quite an expensive alternative if you do not need its minimum 500 users. Then again, it's quite disruptive to migrate to a new tool, isn't it? No one wants to interrupt their workflow by changing tools — especially one that is so central to daily operations. But it does not have to be so scary.
The purpose of a DevSecOps checklist is not to list every single action and practice you should take to ensure that DevSecOps pipeline is effective. Rather, the purpose is to help you establish the right sort of DevSecOps mindset. DevSecOps is more than a collection of best practices, it’s a shared mindset that security is the responsibility of everyone on your team.
The rapid pace of updates and upgrades to operating systems, software frameworks, libraries, programming language versions – a boon to the future of fast-paced software development, has also come to slightly bite us in the back because of having to manage these very many dependencies with their different versions across different environments.
