Systems | Development | Analytics | API | Testing

We recently helped our customer Holocafé prepare its Laravel application for a TV appearance on the German edition of Dragons’ Den (Höhle der Löwen) and the corresponding peak in traffic. The primary change was to utilize Cloudflare as an HTTP reverse proxy to cache the main page of the site and a few other mostly static pages that users were most likely to click on. The expectation was that 80-90% of the curious users could be served with pages from the HTTP cache.

In applications that use closures excessively, understanding stack traces as part of the debugging experience has historically been complicated by the fact that the names of closures did not include the source location. In a PHP stack trace, whenever a frame was represented by a closure, it only contained the reference {closure} and the namespace the closure was declared in, leading to all closures within a namespace looking identical.

Every so often, a careful profiling analysis of your application detects the bottleneck in third-party code and there is little remedy for you to override or change that code. In this blog post I want to present a solution to fixing performance problems in third-party libraries by using the composer patches plugin. I use the the Symfony ErrorHandler as an example.

We strive to improve clarity and user-friendliness, and have thus focused our efforts on several features that align with this objective. Our new Sidebar Menu, the Release Tracking Feature and an increased comparison range for Releases and Markers as well as the possibility to show error messages in notifications all fall into this category. Summary.

In the last few years, there has been a lot of movement around new and exciting PHP testing tools. While this is great news, stepping back a little and understanding the underlying concepts before jumping in is vital to writing great PHP tests. When we talk about testing tools and methodologies, we're referring to automated testing tools. Writing code that tests your PHP apps is a great way to build confidence that your application will behave as you expect.

Tideways is joining the Open Source Pledge because we want to make a public commitment on our various open source contributions. Not only do we rely on open source software in our product Tideways, we are also building our business on top of the open source language PHP and its continued success. The mission of the recently started Open Source Pledge initiative is to establish a new social norm in the tech industry of companies paying Open Source maintainers.

The upcoming PHP 8.4 release will include the brand-new feature “property hooks”, a mechanism to add logic to a class property when read from or written to. One benefit of this feature is that you do not need to protect property access with a private property and public getter/setter methods anymore. You can find out how this feature works in the RFC and other places, but in the spirit of this blog we want to focus solely on the performance implications.

In the web development world, speed and performance are must-haves. Whether you're building a static website, software-as-a-service (SaaS), or bespoke web software, it's important that everything loads quickly to keep your users happy. One of the most common ways to optimize for speed in Laravel is caching. Caching refers to the practice of storing data inside a "cache" or high-speed storage layer.

Sometimes, performance is the primary requirement when you are picking a third-party library to solve a task in your application. For CPU intensive work, there are often similar alternatives that you can choose from: To find out which one of them is more performant for your use-case, you can set up an experiment with microtime/hr_time calls and run them against each other. But: this provides fewer insights than running your tests directly with a Profiler such as XHProf or Tideways!

When using MySQL and InnoDB you will inevitably run into lock timeouts sometime, somewhere. We have recently started seeing this with some of our Shopware 6 customers in their storefronts or worker queues, so I was reminded to go back to 2017 in our codebase when we put a fix in place. In our case, this happened on tables that were constantly written to from many different sources in the code base.