Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Digital Transformation and Modernization with IBM API Connect
  • Toc
  • feedback
Digital Transformation and Modernization with IBM API Connect

Digital Transformation and Modernization with IBM API Connect

By : Bryon Kataoka, Brennan, Aggarwal
5 (5)
close
Digital Transformation and Modernization with IBM API Connect

Digital Transformation and Modernization with IBM API Connect

5 (5)
By: Bryon Kataoka, Brennan, Aggarwal

Overview of this book

IBM API Connect enables organizations to drive digital innovation using its scalable and robust API management capabilities across multi-cloud and hybrid environments. With API Connect's security, flexibility, and high performance, you'll be able to meet the needs of your enterprise and clients by extending your API footprint. This book provides a complete roadmap to create, manage, govern, and publish your APIs. You'll start by learning about API Connect components, such as API managers, developer portals, gateways, and analytics subsystems, as well as the management capabilities provided by CLI commands. You’ll then develop APIs using OpenAPI and discover how you can enhance them with logic policies. The book shows you how to modernize SOAP and FHIR REST services as secure APIs with authentication, OAuth2/OpenID, and JWT, and demonstrates how API Connect provides safeguards for GraphQL APIs as well as published APIs that are easy to discover and well documented. As you advance, the book guides you in generating unit tests that supplement DevOps pipelines using Git and Jenkins for improved agility, and concludes with best practices for implementing API governance and customizing API Connect components. By the end of this book, you'll have learned how to transform your business by speeding up the time-to-market of your products and increase the ROI for your enterprise.
Table of Contents (21 chapters)
close
1
Section 1: Digital Transformation and API Connect
5
Section 2: Agility in Development
15
Section 3: DevOps Pipelines and What's Next

Setting weights, costs, and rate limits

Recall that when your GraphQL schema was established, every field had a resolver. The resolver would fetch the type and populate the field. The resolver could call a database query, a Kafka event, or maybe even another API. How these fetch actions perform should be a concern of yours. For instance, what if the backend resolver requires an extensive query to a database and performance lags? Also, since your graph may have many fields, you could be calling multiple databases and possibly yours or third-party APIs. These are all good reasons why you need to consider how you establish rate limits, as well as determine the cost of your GraphQL queries. Everything has a cost. Luckily for you, the API Connect gateway parses the GraphQL query and determines a cost based on the weights you establish. Let's check these out in the following sections.

Considerations on performance

Understanding what is happening on the backend GraphQL server is...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete