We are happy to announce that our latest version of the Tideways extension (v5.0.22) includes support for the Spryker E-Commerce Platform through fully automated instrumentation and hooks into the core of Spryker. With the complexity of a large E-Commerce project, different channels, multiple language stores and landingpages for campaigns it is especially difficult to get a full view of the performance and errors from within your software as a project manager, developer or system administrator.
With all the customers running Tideways on their Magento, Oxid or Shopware shops I was interested in how in the aggregated average, those shops usually perform on Black Friday compared to the 8 weeks before and the weeks after leading up to Christmas. A lot of e-commerce shops have either large Black Friday, Cyber Monday or week long christmas campaigns, which can increase the traffic to the shops significantly.
A few weeks into year five of the Tideways project we are happy to announce the release of Tideways version 5, including large updates to all parts of the stack from PHP extension, daemon and the user-interface. Ladies and gentlemen, this is Tideways no. 5!
We’re really happy to announce that Bugfender 2.0 went live in last quarter – a long awaited release that brings many feature requests from our users. We’d like to take this opportunity to thank you all for your feedback. It’s truly invaluable and helps us to improve Bugfender every day. As some of you may be aware, the service experienced some occasional down time during June.
We created this resource to solve one basic problem: Once you go through all the work of building an app, how can you be sure to nail the landing? In the rush to get an app out, many developers can forget to tag releases or lose depository information that simply needed to be earmarked for a future update. There are some final security measures that need to be taken to protect your app. Whether it’s due to excitement or fatigue, it happens.
Did you ever have a memory leak in your PHP program and couldn't locate the exact source in your code? From my experience with memory profiling in PHP, this is caused by the PHP engine and how it manages memory. PHP uses a custom memory manager on top of the native memory management in C for multiple reasons...
In 2016, on the eve of the Black Friday sales frenzy in the US, a research firm called Apteligent released a report estimating how much money firms could lose if their apps crashed on the big day. The report tallied up the amount of money spent by retail app customers on Black Friday the previous year and worked out what would happen if every customer experienced at least one crash during peak hours.
I’d like to offer a heartfelt apology to all of our users who have experienced any downtime and issues with Bugfender recently. We’re really sorry these have occured and for all of the inconveniences they may have caused you. We understand that many people rely on Bugfender to help them in their daily duties and that our service has let you down.
Memory profiling in PHP has traditionally been hard. Most memory profilers compare the memory or peak memory before and after a function call to find out how much memory usage increased or decreased. This can be achieved by calling the equivalent of memory_get_usage() and memory_get_peak_usage() functions from within the profiling extension.
