Hello Miguel, first of all congrats for the great explanation. Please Can you send the link for the Next Video "Process of Setup ApigeeX with Shared VPC Model and Backends in Service Projects"
Hey Miguel, is the "Customer Project (Apigee)" needs to be a dedicated project? i.e. separate from backend project. For example, both are owned by same business unit.
Hey Marvin, yes, it's totally fine to have some backend services deployed in the same GCP project, as long as those services are managed by the same team that manages Apigee X. In this case, you won't really need a Shared VPC Architecture since Apigee X would not need to reach to services running in other projects. If you do go with this approach, later if you do need to talk from Apigee X to services in other projects, you will need to use Private Service Connect for the southbound connectivity
Hello Miguel, first of all congrats for the great explanation. Please Can you send the link for the Next Video "Process of Setup ApigeeX with Shared VPC Model and Backends in Service Projects"
This is amazing. Thanks, Miguel !!
Hey Miguel, is the "Customer Project (Apigee)" needs to be a dedicated project? i.e. separate from backend project. For example, both are owned by same business unit.
Hey Marvin, yes, it's totally fine to have some backend services deployed in the same GCP project, as long as those services are managed by the same team that manages Apigee X. In this case, you won't really need a Shared VPC Architecture since Apigee X would not need to reach to services running in other projects. If you do go with this approach, later if you do need to talk from Apigee X to services in other projects, you will need to use Private Service Connect for the southbound connectivity