This past week some of the Scout team had the opportunity to hang out at PyCon USA in Cleveland. This was the first time the Scout APM team had attended PyCon. It was great to spend some time with an awesome swath of the Python community. With a great booth location situated across the aisle from the innovative and fun Slack booth, we had fun getting to know everyone with a solid amount of traffic heading past our booth over the exhibition days.

This article is a follow up of our previous article where we explain how we deployed a Kubernetes cluster with k3s on a Raspberry Pi cluster.

Some time ago, the Register published an article titled “Lambda and serverless is one of the worst forms of proprietary lock-in we’ve ever seen in the history of humanity”. It received a lot of attention, and vendor lock-in has become a perennially popular question at conferences. But I’m here to tell you that you are probably thinking about vendor lock-in all wrong when it comes to serverless.

Microservices and containers multiplied the complexity of Ticketmaster’s software system. Its engineers solved their debugging problems with Jaeger, an open-source tracing tool from Uber incubating at CNCF.

These days we spend a lot of time talking about modernizing our stack, modernizing our architectures, using new application components, modern application life cycles, etc. So, what is this all about and why do we spend so much time talking about it? First, there is a lot of self-serving vendor speak involved…starting with cloud providers and closely followed by open source commercialization shops and commercial ISVs (ourselves included) who have to spin the world in their own image.

When it comes to monitoring your user experience, it is easy to monitor and optimize just the landing pages. But, does your user’s journey end at the landing page? No. Monitoring your user journey goes deep. Each click the user makes on your site or service needs to work and be as fast and responsive as the initial page load.