API Designing, Prototyping, and Testing: Everything Must and Will be Transformed into an Application Programming Interface (API)

Everything must and will be transformed into an Application Programming Interface (API). Every digital and physical asset and item on the globe must be controlled and communicated with. To make this happen, we need to make every digital asset programmable, thereby turning everything into an API. The world is on track to have a trillion programmable endpoints in the near future.

This learning repo is part of Bootcamp 2021

The Future of Software Development and APIs, with Postman CTO Ankit Sobti

REST vs GraphQL

What is GraphQL?

You can follow a number of differnt workflows in developing an API.

We suggest that you should follow this workflow when designing and developing an API and an application:

1. Start by define an API specification (Step 04)
2. Generate a collection from it.
3. Once you have a collection, you can create a mock server from it (step 05)
4. Your UI Application team can now start developing an UI application by using the mock server.
5. Your API developing team can now start developing the actual API implementation in the parallel to the UI application. There are many options, we recommend that you do develop serverless APIs. In case of REST implementation by using AWS Gateway and Lambda Functions and GrpahQL using AWS App Sync and Lambda Functions using AWS CDK in TypeScript.
6. Once the API implementation and development implementation is complete you can change the URL in your UI application and test collections from the mock URL to the implementation URL.
7. During development you can run collections on the command line with Newman and integrate it with your CI/CD e.g. Google Actions.

Note:

To Learn how to develop the Serverless Cloud APIs visit the Panacloud Serverless CDK Repo

If you want to learn to develop SaaS and UI applications using APIs visit Bootcamp 2020