Managing an application’s performance, and specifically keeping it in good condition, is one of the hardest challenges in software development. That’s true for virtually any programming language and platform. Java is no exception to this rule. But beyond that, Java also presents some unique challenges of its own.
DevOps is a tech industry buzzword that refers to the collaboration of a software development team and operations teams within a company. The results are a Development + Operations team, a DevOps team. While it’s a buzzword, it also represents a new shift left standard that’s starting to take hold in the software development industry.
Equality is an essential concept when programming, not only in Java but in pretty much all programming languages. After all, much of what we do when writing code has to do with comparing values and then making decisions based on the results of such comparisons.
Chef and Puppet are two popular tools for configuration management. These type of tools help engineers to maintain a consistent configuration in all servers. For instance, all servers might need to have IIS with a binding to port 443 for HTTPS access and the respective firewall rule for inbound traffic. More importantly, if anyone removes the firewall rule, these type of tools will keep consistency by creating the firewall rule again.
Need help on how to monitor IIS? This guide covers the basics, including HTTP ping checks, IIS Application Pools, and important Windows Performance Counters. We’ll also take a look at how to use an application performance management system to simplify all of this and get more advanced IIS performance monitoring for ASP.NET applications.
An optimized DevOps process flow is vital for DevOps teams. It allows for seamless development and operations integration through the implementation of the CICD pipeline for development, deployment, and feedback.
You’ve probably seen mentions of Docker over the past few years. This guide explains the basics so you can get up and running with Docker for PHP in your local development environment.
Exception handling in Java isn’t an easy topic. Beginners find it hard to understand and even experienced developers can spend hours discussing how and which Java exceptions should be thrown or handled. That’s why most development teams have their own set of rules on how to use them.
It’s one thing to write code that works. But what about clean, readable, concise code? That’s another thing entirely. To create an app that solves one problem? Not that hard. What about one that not only solves the problem, but it’s also easy and pleasurable to use? Now we’re talking. You could apply the same reasoning for many software properties, which would make for a long article. Instead, let’s focus on only one of those properties: performance.
Software is a complex thing. As soon as you deploy an application to production—especially when you don’t have any control over the environment it’s running on—anything could happen. You’ve created this “monster” and set if free. It’s now free from your control. How do you tame this beast before it creates havoc? The first step is to trace its steps (no pun intended).
