You are here

Best of TechBeacon 2015: Top 10 performance stories

public://pictures/mike-head-new_2_0.jpg
Mike Barton, Managing Editor, TechBeacon

It's not just a hashtag on Twitter: Application performance really does matter. The time o move to performance engineering is now, and TechBeacon is with you, providing expert guidance and how-tos, as well as enterprise thought leadership. In addition to our 40-page report, the State of Performance Engineering 2015-16, Performance has been one of our most rich categories, anchored by TechBeacon's resident expert, Todd DeCapua.

Here are our top 10 performance stories from 2015:

[ Get up to speed on quality-driven development with TechBeacon's new guide. Plus: Download the World Quality Report 2019-20 for lessons from leading organizations. ]

102 performance engineering questions every development team should ask

Performance engineering is a complex discipline encompassing applications, infrastructure, security, and more. To truly optimize your performance, your organization needs to address a broad range of issues. To make informed decisions, individuals and organizations need to ask themselves these 102 questions.

[ Get up to speed with TechBeacon's Guide to Software Test Automation. Plus: Get the Buyer’s Guide for Selecting Software Test Automation Tools ]

Testing fail: How performance engineering can help dev avoid disaster

The initial failures of the Healthcare.gov website revealed how fragile underlying systems and integrated dependencies can be. Simple performance testing isn't enough. If you don't develop and test using a performance engineering approach, the results can be both costly and ineffective.

10 totally avoidable performance testing mistakes

Performance testing is an important component of performance engineering. Unfortunately, not everyone executes performance testing processes correctly. Here are 10 of the most common mistakes organizations make—and how you can avoid them.

The essential guide to improving mobile performance

Mobile performance is an increasingly complex domain but generally includes four main components: app performance, network performance, server performance and API performance. By focusing on these areas, you can address two key metrics: Rendering time of the content on the screen (such as a web page loading or an app starting), and the time to consumer interaction with the content on the screen.

Don't do performance testing (without a plan)

You have a new code release and two weeks for performance testing. What tests do you run? One common answer is to run the same tests you used on the last release (after fixing your scripts, of course). This is a good way to make sure the new release can handle the same load as the last one. However, this approach ignores a key fact: loads change.

Java performance tools and teams survey: Who is doing what?

What's the best way to tune Java performance? That's a complicated question, and RebelLabs has a ton of answers in its just-released sixth annual Developer Productivity Report. Here are some top takeaways.

Power combination: Synthetic and real device app monitoring

If your mobile app doesn't work—or works badly—you're losing money and damaging your reputation. That's why application monitoring is a must-have for nearly every organization. But simply deploying a monitoring system isn't enough; you must use the right tools to monitor the right functions.

23 front-end performance rules for web applications

Like most things in life, web applications have rules you should follow. The 23 performance engineering best practices below will help you optimize the user experience and get the best business results.

App for that? IT monitoring tools are in need of a major upgrade

Too many IT monitoring tools are out of date. While applications are migrating to complex, dynamic virtual and cloud environments, many tools are stuck in a physical server mindset. This trend is driving the need for simpler, more intelligent tools to help understand and optimize the infrastructure for application service delivery.

How microservices broke monitoring (and how to fix it)

Microservices present big problems for monitoring. Instead of keeping tabs on a single monolithic application, IT operations now have to contend with dozens, hundreds, or even thousands of modules interacting in complex patterns. To meet this challenge, IT Ops needs a fundamentally new approach to monitoring, one that provides end-to-end inclusivity and can provide granular insights into each service.

 

[ Learn how to apply DevOps principles to succeed with your SAP modernization in TechBeacon's new guide. Plus: Get the SAP HANA migration white paper. ]