API Performance in 2016: New Insights for Organizations that Develop and Consume APIs

Priyanka Tiwari
Learn more about SmartBear

When it comes to developing, deploying, and maintaining a truly powerful application, performance needs to be a top priority.

But that performance isn't only limited to the software your team builds and maintains. Moreover, the performance of an application depends on the performance of the APIs that power it.

SmartBear Software recently released the results of a global API survey, which includes responses from more than 2,300 software professionals in over 50 industries, across 104 countries around the globe.

The report included input from both API providers — organizations that develop and deploy APIs — and API consumers — organizations that use APIs to power their applications or internal systems.

When Asked: Why Do You Consume/Use APIs?

■ 50% said they use APIs to provide interoperation between internal systems, tools, and teams

■ 49% said they use APIs to extend functionality in a product or service

■ 42% said they use APIs to reduce development time

■ 38% said they used APIs to reduce development cost

It's clear to understand the impact that poor API performance could have on any of these use cases. Which is why it's not surprising that, when asked about how they would react upon encountering an API quality or performance issue, one-third of consumers said they would consider permanently switching API providers.

Whether you work in an organization that develops APIs, or have tools and systems that depend on APIs — performance should matter to you.

How Can You Ensure API Performance?

Just like you use tools to test and monitor your application, you also need to invest in the right tools for testing and monitoring your API. Whether you're launching an API of your own, or are concerned about the third party APIs that power your applications, you need to understand how your APIs are performing. You also need to understand the capacity of these APIs so that you can determine the amount of volume your applications can handle and adjust as necessary.

In most cases, ensuring API performance begins with load testing your API to ensure that it functions properly in real-world situations.

By utilizing specialized testing software, load testing allows testers to answer questions like:

"Is my system doing what I expect under these conditions?"

"How will my application respond when a failure occurs?"

"Is my application's performance good enough?"

But if you're performance strategy ends there, you could still be at risk of costly performance problems. This is where monitoring comes in.

API monitoring allows you to determine how your APIs are performing and compare those results to the performance expectations set for your application. Monitoring will enable you to collect insights that can then be incorporated back into the process. Once you've created your monitors and established your acceptable thresholds, you can set up alerts to be notified if performance degrades or the API goes offline.

Monitoring is Critical for Identifying and Resolving API Performance Issues

One of the key findings from the State of API 2016 Report is that a majority of API providers still face setbacks when it comes to resolving API performance issues.

Less than 10% of API issues are resolved within 24 hours. Nearly 1-in-4 API quality issues (23.9%) will remain unresolved for one week or more.

The biggest barrier to resolving API quality issues is determining the root cause (45.2%), followed by isolating the API as being the cause of the issue (29%).

A premium synthetic monitoring tool enables you to monitor your internal or 3rd party APIs proactively, from within your private network or from across the globe. A monitoring tool will help you find API and application issues, engage experts in a timely manner and fix issues before they impact your end users. If you are using external 3rd party APIs for your mission critical applications, a tool can help you monitor SLAs and hold your vendors accountable in case of unavailability or performance degradations.

Priyanka Tiwari is Product Marketing Manager, AlertSite, SmartBear Software.

Related Links

Hot Topics

Related Vendors

The Latest

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

API Performance in 2016: New Insights for Organizations that Develop and Consume APIs

Priyanka Tiwari
Learn more about SmartBear

When it comes to developing, deploying, and maintaining a truly powerful application, performance needs to be a top priority.

But that performance isn't only limited to the software your team builds and maintains. Moreover, the performance of an application depends on the performance of the APIs that power it.

SmartBear Software recently released the results of a global API survey, which includes responses from more than 2,300 software professionals in over 50 industries, across 104 countries around the globe.

The report included input from both API providers — organizations that develop and deploy APIs — and API consumers — organizations that use APIs to power their applications or internal systems.

When Asked: Why Do You Consume/Use APIs?

■ 50% said they use APIs to provide interoperation between internal systems, tools, and teams

■ 49% said they use APIs to extend functionality in a product or service

■ 42% said they use APIs to reduce development time

■ 38% said they used APIs to reduce development cost

It's clear to understand the impact that poor API performance could have on any of these use cases. Which is why it's not surprising that, when asked about how they would react upon encountering an API quality or performance issue, one-third of consumers said they would consider permanently switching API providers.

Whether you work in an organization that develops APIs, or have tools and systems that depend on APIs — performance should matter to you.

How Can You Ensure API Performance?

Just like you use tools to test and monitor your application, you also need to invest in the right tools for testing and monitoring your API. Whether you're launching an API of your own, or are concerned about the third party APIs that power your applications, you need to understand how your APIs are performing. You also need to understand the capacity of these APIs so that you can determine the amount of volume your applications can handle and adjust as necessary.

In most cases, ensuring API performance begins with load testing your API to ensure that it functions properly in real-world situations.

By utilizing specialized testing software, load testing allows testers to answer questions like:

"Is my system doing what I expect under these conditions?"

"How will my application respond when a failure occurs?"

"Is my application's performance good enough?"

But if you're performance strategy ends there, you could still be at risk of costly performance problems. This is where monitoring comes in.

API monitoring allows you to determine how your APIs are performing and compare those results to the performance expectations set for your application. Monitoring will enable you to collect insights that can then be incorporated back into the process. Once you've created your monitors and established your acceptable thresholds, you can set up alerts to be notified if performance degrades or the API goes offline.

Monitoring is Critical for Identifying and Resolving API Performance Issues

One of the key findings from the State of API 2016 Report is that a majority of API providers still face setbacks when it comes to resolving API performance issues.

Less than 10% of API issues are resolved within 24 hours. Nearly 1-in-4 API quality issues (23.9%) will remain unresolved for one week or more.

The biggest barrier to resolving API quality issues is determining the root cause (45.2%), followed by isolating the API as being the cause of the issue (29%).

A premium synthetic monitoring tool enables you to monitor your internal or 3rd party APIs proactively, from within your private network or from across the globe. A monitoring tool will help you find API and application issues, engage experts in a timely manner and fix issues before they impact your end users. If you are using external 3rd party APIs for your mission critical applications, a tool can help you monitor SLAs and hold your vendors accountable in case of unavailability or performance degradations.

Priyanka Tiwari is Product Marketing Manager, AlertSite, SmartBear Software.

Related Links

Hot Topics

Related Vendors

The Latest

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...