roundup

Below, we’ve lassoed the posts you need to read from us. Check out what our authors are writing about in this week’s digest.

Data Compliance: What It Is and Why You Should Care

Do you remember what Uncle Ben said to young Peter Parker? “With great power comes great responsibility.” The same applies to companies. At present, businesses hold a huge amount of data—not only the data of a company but also of employees and customers. So Arnab Roy Chowdhury is here to help you explore what data compliance is and who should care about it. Learn more on Enov8’s blog. 

DevOps Toolchain, Clearly Explained: The What, Why, and How

Revolutionary companies have their ideas valued when they convert them into products. But the entire conversion process is a thorny path. With DevOps being implemented in many organizations, the DevOps toolchain has made this process much simpler. In this post on Plutora’s blog, Omkar Hiremath is here to talk about how various DevOps tools have made the software development life cycle manageable. Check it out here. 

Popular Ruby Libraries

Ruby on Rails Gems is a package manager containing libraries, software packages, and utilities for standard format distribution of  Ruby programs and libraries. RoR Gems have functionality with related files to help save time in web development. Find out more on Stackify’s blog from Harikrishna Kundariya.

It’s time for yet another post in our series about how to get up to speed with logging. In this post, you can learn about Groovy logging. Despite Groovy not being an obscure language, it’s certainly less well know than languages like Java, Python, Ruby, or JavaScript. Find out more from Carlos Schults on Scalyr’s blog.

How and Why to Monitor Logs: All You Need to Know

Logs. You have them. You need to keep track of them. The process of log monitoring can be tedious. Typically it’s one of those things we take for granted and only look at when it stops working. So, how do you deal with them? This post also can tell you about why and how to monitor logs. Guillermo Salazar can fill you in on XPLG’s blog.

We also updated a few posts, like this one on Opencensus. Debugging problems in a distributed system is not an easy task, especially when the application is running in production and not all of your customers are having problems. But as was once said on Twitter, if debugging is hard, it’s “probably because you aren’t instrumenting your code enough.” Instrumentation is how your applications produce the events that will help you to have a better understanding of a problem when debugging in production. At debugging time, it’s too late to regret not including more debug code lines in the application. That’s why you need to instrument your code with OpenCensus as soon as possible—so that when debugging time comes around, you’ll have everything you need. Learn more on Scalyr’s blog. 

.NET Performance Optimization: Everything You Need To Know

It’s Friday afternoon, the majority of the development staff has already packed up and headed home for the weekend, but you remain to see the latest hotfix through to production. To your dismay, immediately after deployment, queues start backing up and you begin to get alerts from your monitoring system. Something has been broken and all evidence points to an application performance bottleneck. This experience is all too common for developers and software team managers. But maybe there’s a solution. Find out more on Stackify’s blog.