Book Image

Digital Transformation and Modernization with IBM API Connect

By : Bryon Kataoka, James Brennan, Ashish Aggarwal
Book Image

Digital Transformation and Modernization with IBM API Connect

By: Bryon Kataoka, James Brennan, Ashish 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)
1
Section 1: Digital Transformation and API Connect
5
Section 2: Agility in Development
15
Section 3: DevOps Pipelines and What's Next

Chapter 9: Building a GraphQL API

So far, you have been learning about how to create APIs that provide defined payloads. You have learned about how to utilize existing backend services to deliver data to consumers through REST and SOAP APIs. If your services have been in existence for a while, you may have had situations where you need to update those services with either new business requirements or additional data elements. Perhaps you've even had situations where you have shared your APIs with different business partners and each required the same API but with different requirements. In those cases, you may have created new APIs or updated the APIs to support the additional business requirements for multiple consumers. In either of those cases, versioning would have been required.

Managing multiple versions of APIs can complicate your API strategy. That is the price you pay when you develop and support many versions of APIs. In this chapter, you will be introduced to GraphQL...