DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • Rocket.rs API Demo Implementing Header-Based API Key Protection
  • REST APIs: Simplicity, Flexibility, and Adoption
  • API Testing With Cypress
  • What Is the Difference Between API Rate Limiting and Throttle Controls?

Trending

  • Unleashing the Power of Microservices With Spring Cloud
  • What Is Kubernetes RBAC and Why Do You Need It?
  • Top 7 Best Practices DevSecOps Team Must Implement in the CI/CD Process
  • Exploring Sorting Algorithms: A Comprehensive Guide
  1. DZone
  2. Data Engineering
  3. Databases
  4. Showing the Response Times for Individual Requests in the Axway/Vordel API Server

Showing the Response Times for Individual Requests in the Axway/Vordel API Server

Mark O'Neill user avatar by
Mark O'Neill
·
Aug. 08, 13 · Interview
Like (0)
Save
Tweet
Share
4.85K Views

Join the DZone community and get the full member experience.

Join For Free
When managing APIs, one of the most important requirements is to perform a root cause analysis of any API bottlenecks. Remember that the APIs that you expose to your clients may themselves rely on other APIs.


Let's say that you are exposing an API on an API Gateway that in turn calls out to SalesForce APIs. If your own API is running slowly, you need to be able to isolate the reason. Here, in the web interface to the API Server, I am looking at the transaction and I see two call-outs to SalesForce APIs. The second one, to the SalesForce log-in service, is taking a long time (see the timings circled in red below).


We see at a glance each input and output message being sent to the API, and we can also look at the request and the response to the client calling the API at the API Server. This allows you to pinpoint the cause of any delay and see message timings at a fine-grained level.

You can then go one step further. If you click on the Filter Execution section and expand it, you can see exactly the timing of each step in the API Server. I've highlighted the step where we call out to SalesForce to log in to SalesForce. We can see that that step is taking a long time, whereas other steps within the API Server are very fast.


We've tried to make it very simple to see not only how long a transaction takes but also how long each step in the transaction takes. So if a client says "my API calls are too slow!" you can look at the API Server's web interface and see the reason at a glance. Then, you can take action (e.g. enable distributed caching, or add proactive load-balancing across multiple APIs).
API Requests

Published at DZone with permission of Mark O'Neill, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Rocket.rs API Demo Implementing Header-Based API Key Protection
  • REST APIs: Simplicity, Flexibility, and Adoption
  • API Testing With Cypress
  • What Is the Difference Between API Rate Limiting and Throttle Controls?

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: