Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Apigee edge limits and performance extension Google cloud Pub/Sub

Hello guys, I'm doing a study to define the design of the use of Google cloud Pub/Sub through the standard extension of Apigee for communication with GCP.

Reference links:

https://docs.apigee.com/api-platform/reference/extensions/google-cloud-pub-sub/google-cloud-pub-sub-...

https://cloud.google.com/iam

1 - After setting up I created a service account at GCP: https://cloud.google.com/iam/docs/service-accounts

Apigee Publisher:

Through ExtensionCallout policy I can post messages directly to a Google Cloud Pub/Sub topic.

Because the scenario I need to apply is 1 proxy api for 1 pub/sub.

So with this design it does not impact my operation if I need to do some maintenance on the service accounts.

But using this approach I would have a structure (1 account per api proxy * environments), for example:

  • gcp-caller-prd
  • gcp-caller-hml
  • gcp-caller-dev

I searched the forums and documentation on performance and limits of the above approach and did not find clear documentation on the subject.

My question is:

Are there limits on communication extensions with Google cloud Pub/Sub that can be configured in the apigee?

Can there be any performance problems if you use this approach in the apigee tool?Is there a better approach for this scenario?

Does anyone know a contraindication for this scenario?

0 3 269
3 REPLIES 3