Let’s begin with a little thought experiment. Imagine you’re responsible for the next release of your company’s flagship product, and today is the big day: you’re about to give a demo presentation for all the big shots in the company. The CTO is obviously there, since she’s your boss. The CEO is there as well, along with the VP of Marketing and some of the company’s investors. So, that’s your boss, your boss’s boss, and the moneymakers.
Whether you’re the consumer or producer of an API, you’ve no doubt seen that good error handling can make debugging easier. And you may have noticed that error handling works best when everyone speaks the same language and has the same expectations. But what makes for good error handling? And how can we implement it and ensure consistency across our application?
Picture this: you’re standing in the largest meeting room in your company. Behind you, a huge LED monitor. In front of you, all members of the C-suite. The CTO, your direct boss, is visibly nervous. The CEO looks interested and somewhat excited. The CFO looks happier than usual, though it probably has more to do with his very successful golf round the day before and nothing to do with the presentation you’re about to give.
I use performance monitoring tools primarily to find slow and buggy code. At the start of development, I typically use the tools more for finding software bugs. Once the codebase is at a relatively stable phase, then I shift my focus toward finding less performant code. Which is why I turn to tools like Retrace to help with profiling for better performance.
Microsoft’s cloud-based platform Azure has helped many businesses expand and cut back on their costs associated with hosting and storing data on a traditional server. Furthermore, the platform has given developers a chance to create, manage, and deploy powerful applications capable of assisting cloud customers to perform any number of tasks. From handwriting recognition to text sentiment analysis and Bing ad-free image search, Azure’s ML-based services spans many areas.
When developing a web application based on PHP, it’s not enough to just solve the problem and project requirements. Server resources like storage, memory, and number of CPUs contribute to the price of the hosting; that’s why developers should take into consideration these resources when developing web applications. On top of all of these, the application must run smoothly.
Stackify was founded with the goal of giving developers the all the tools they need to troubleshoot and monitor their applications. We are very excited to announce that we now have support for PHP monitoring to go along with support for .NET and Java applications.
To all the developers out there, it is highly advisable that every application you build should have tools that will monitor performance and ensure that it runs correctly. There are a variety of tools available that can monitor your application’s performance. Choosing the right tool that caters to your organization’s needs should be a priority.
Background: Boston Software was long overdue for an affordable, reliable APM solution that could provide deep and credible insight into the behavior of its services. Customers began reporting an issue with the software, but traditional monitoring was unable to pinpoint the source.
When you spend a long time building an app or website just to have users complain about latency issues, it sucks. You don’t know where the problem lies, nor do you know the environment in which it occurred. So it gets ignored, and performance issues keep lingering. This not only wreaks havoc on the end users, but your bottom line suffers as well.
