OIC allows us to directly publish endpoints to an OCI API Gateway -
The OIC developer chooses the Gateway and also chooses name and path prefix. This results in a new deployment to the Gateway -
Now this demos very well, but do we really want OIC developers doing this? This may suffice for some use cases, however, many organizations have API administrators whose task it is to expose apis to 3rd parties, adhering to company policies, which could include naming conventions, api granularity and policies to be applied.
Also API Gateway has a limit of 20 deployments per gateway -
You can check out the api gateway resource limit docs here. We can, however, have multiple routes within a deployment -
This gives us the possibility of up to 1000 apis per gateway, which is sufficient for the vast majority of OIC customers.
Let's see how such use of deployments could work.
I create a deployment in API Gateway called CX -