PHP powers millions of applications. This massive success is due to PHP’s simplicity, clear documentation, and tons of free resources. The PHP community provides an incredible ecosystem of libraries and tools, enabling anyone to develop production-grade apps rapidly. What’s even more exciting is PHP projects are cheap to host and widely supported by many platform providers such as Heroku.
Robust application logging is central to any quality strategy. Unfortunately, many quality strategies fall short, implementing logging in a less than stellar way. Java application logging is no different. And since we’re talking about one of the most popular programming languages, investments in improving the overall Java logging strategy could pay off many dividends in the future.
There are a lot of “cloudy” terms out there now. Is cloud-native better than cloud-based? Am I considered in the “cloud” when my application is cloud-enabled? Let’s take a closer look at the difference between cloud-native, cloud-based, and cloud-enabled to tease apart these different terms.
After the introduction of Docker, the life of a developer became much easier. Kubernetes solved many problems and offloaded the task of setting up the necessary runtimes, libraries, and servers. Kubernetes even simplified complex deployments and made managing multiple containers for bigger applications within the reach of most developers.
Like with any software application, maintaining the app after deployment is critical. It’s important to have methods to check its status when issues inevitably arise. One of the first things most technical professionals will do when diagnosing issues is to check the logs. This way, you can dig deeper into an issue and determine the root cause.
As an IT professional, you’ll find log messages are one way to catch errors and solve your problems. As much as log messages are helpful, they can be confusing because a lot of messages—even the log messages you don’t need to see—are generated by the server. Instead of making your life easier, log messages can make things harder for you because unnecessary error messages are being logged.
Firewalls are a critical part of any organization’s defense in depth strategy. They serve a key role in protecting your network against malicious actors, and they do this well. But they also have a dirty little secret.
Routers play a key role in any network. If you’re like most network engineers, you usually spend most of the time working with routers (as opposed to other network devices). In smaller networks, routers may even be the only devices managing traffic. Router logs can tell you a lot about your network. In this post, we’ll walk through how to analyze router logs efficiently.
When apps crash, they generate logs containing information related to where the issues causing the crash occurred. Looking at these logs is a great place to start your effort toward diagnosing and fixing the crash.
Docker changed the way developers build software. It solved many issues, but bugs can still occur. When this happens, the first step in the debugging process is usually to read logs. However, when using Docker, this isn’t as straightforward as you may think. You can simply execute docker logs [container_id], but it’s not always possible to use this command, and it’s not an ideal solution for bigger applications. In this post, you’ll learn the pros and cons of the different logging options and what to consider when choosing a logging strategy in Docker.