Operations | Monitoring | ITSM | DevOps | Cloud

In 2016, Google released the definitive book on Site Reliability Engineering (SRE) - a practice that had originated in the company to take care of a monumental problem - how to keep the Google services running with high reliability. Over the years, SRE has been widely adopted by dev teams across the globe and is a popular role at startups and enterprises alike. Here is a look at how search for SRE has trended over the years.

Spring Boot is the most popular Java framework, with over 50 percent of developers using it. Java engineers working in the spring framework can deploy web applications quickly, without the need for a separate server. Spring focuses on speed, simplicity, and productivity. It uses Inversion of Control, or IoC, and dependency injection to increase modularity and enable loose coupling. Spring Boot builds off of the spring framework.

The current big data world allows even tiny IT environments to produce massive amounts of information. After determining how to open up various data generation sources, a business analyzes the information. Here, the analysis method you leverage varies depending on the data, the tools/equipment used, and the use case. A good practice is to visualize the traces, weather logs, data, or metrics.

Deploying infrastructure manually is an outdated practice. Using Terraform to automate manual deployment is the new normal. In this blog, we have explained in detail, how to create your first module using Terraform. Before the advent of cloud and DevOps, most companies managed and deployed their infrastructure manually. This used to be risky because not only was it error-prone, it also slowed down the entire infrastructure cycle.

Monitoring for uptime is becoming increasingly necessary as SaaS and Always-On services integrate deeper with our professional and personal lives. When bottom lines and infrastructure requirements are tied so closely to 24/7 accessibility, making sure your websites are UP becomes priority one. We’ve scoured our support tickets, talked to our users, and kept an ear to the ground to compile the top 10 questions surrounding uptime monitoring and break down the answers.

In this episode Jason is joined by John Martinez, Director of Cloud R&D at Palo Alto Networks, to talk about the FinOps Foundation and the vast range of optimization opportunities to reduce spend in the cloud. John comes in with some extremely useful insights into how FinOps is laid out and their use of a “crawl, walk, run approach.” John and Jason discuss multi cloud and go into the specifics on the costs associated with multi cloud as well the security changes that will come with.

Load testing isn’t an engineer’s favorite task. Every setup choice made during performance testing will yield varying results. The chosen load test protocol is the difference between an application that performs well under most circumstances and one that buckles at hidden stress points. Yet failing to run adequate tests isn’t an option when dealing with a complex API architecture. Needless to say, all your load testing options must be carefully evaluated.

When was the last time you thought about your backup process? Is it one of those things you’ve just accepted to be the way it is? If so, your backup may be consuming more time and resources than it should. The state of backup technology has moved forward, and many of the old assumptions about it are no longer true. N-able recently interviewed about a dozen MSPs from around the world and heard first-hand what they discovered when they took a fresh look at backup.

IT Pro Day is here, and it feels like the new year in IT! It’s a time to reflect on lessons from the past year and celebrate your achievements while setting goals for the season ahead. The theme for this year, Bring IT On, feels especially appropriate as we’ve been in the Year of the Ox. According to the Chinese zodiac, the ox is known as the “good helper” symbolizing strength, diligence, and persistence. I can’t think of a better sign that embodies IT pros.

To release reasonably secure products, vendors must integrate software security processes throughout all stages of the software development lifecycle. That would include product architecture and design; implementation and verification; deployment and monitoring in the field; and back again to design to address the changing threat landscape, market needs, and product issues.