PHP is one of the most popular server-side scripting languages for building web applications because it’s easy to use. No matter what you build, making it easy to log errors is key to ensuring a short code-test-learn feedback cycle.

There’s no denying it — Kubernetes has become the de-facto industry standard for container orchestration. In 2018, AWS, Oracle, Microsoft, VMware and Pivotal all joined the CNCF as part of jumping on the Kubernetes bandwagon. This adoption by enterprise giants is coupled by a meteoric rise in usage and popularity. Yet despite all of this, the simple truth is that Kubernetes is hard.

Logging provides critical value to applications with insight to usage, stats, and metrics, and saves us when debugging a problem. But we often leave logging to poorly implemented afterthoughts. So what should we know to get the most out of our logging? We will look at the Rails logger and some logging best practices.

It’s Sunday afternoon, and you’re having a nice relaxing weekend, sitting down watching your favorite sporting event. While enjoying the game, you get a high alert email on your phone, noting something’s going on and you need to jump into action. What do you do in these high stress times? Every second counts, and everyone is waiting on you to tell them what’s happening.

With sessions on cloud, big data, and A.I., to training courses, certifications, and hands-on labs, IBM Think 2019 in San Francisco was full of innovation and learning. From talks on emerging technologies and industry trends, the overall theme of the event was clear – IBM is betting on the next chapter of cloud: multi-cloud, Kubernetes, containers, microservices and open-source.