Apigee Developer Portal Kickstart - why use CloudSQL and Firestore?

[VinP]

Hello, I have seen a high-level architecture diagram in the link below of all the main GCP resources used/provisioned by  Apigee Developer Portal Kickstart:

https://cloud.google.com/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-overview

I notice that the set up requires the use of CloudSQL and Firestore. For what reason are these two required and is it necessary to use both? From the Marketplace, it states that 'You can customise the configuration later when deploying this solution.' Does this mean I can remove the use of one of the storage solution or only change configurations like disk size?

I am currently waiting for my organisation to give me permission to use the kickstart so I am unable to test this out. 

Many thanks. 

[kedarkhaire]

Hi @VinP 

Apigee Cloud Marketplace itself doesn't directly require CloudSQL or Firestore. It's a platform where you can find and deploy various API solutions, some of which may use these services as backend databases.

However, if you're building your own API solutions on Apigee, you have the flexibility to choose the database that best suits your needs. CloudSQL and Firestore are both viable options, but they're not mandatory. You could also use other databases or data storage solutions depending on your specific requirements.

Ultimately, the decision to use CloudSQL or Firestore (or any other database) depends on the nature of your API and its specific data storage requirements.

Thanks!

[AlexET]

Hey! Thank you @kedarkhaire for providing such a prompt reply – And thank you @VinP for engaging with the community. We’re happy to have you here!

If the reply solved your question, it would be great if you could mark it as the accepted solution. This helps others in the community easily find the right answers. Looking forward to seeing you around! Don’t forget to check out our latest articles for more resources. 😉

[VinP]

Thanks @AlexET , I will do once I am happy with the solution. 😊

[VinP]

Hi @kedarkhaire , Thank you for your reply.

Just so I understand what you are saying, when deploying the Apigee Developer Portal Kickstart after setting configuration details such as Machine Type and Networking Interface, the deployment will provision both CloudSQL and Firestore (as stated in the jinja file in the Deployment.zip) simply to provide the user with viable storage solution options for the Drupal Portal which the user can then configure/remove after deployment. Is that right? Meaning after the deployment, I can remove the use of Firestore and just use the CloudSQL instance that it provision?

Many thanks. 

[kedarkhaire · Accepted solution]

Hi @VinP 

Unfortunately, directly removing Firestore from an Apigee Cloud Marketplace deployment after deployment isn't straightforward.

The Cloud Marketplace solutions are designed to be integrated with specific services, including Firestore in some cases. While you might be able to modify the deployed resources to some extent, completely removing a service like Firestore could lead to unexpected behavior or instability.

Here's a more nuanced approach to consider:

1. Evaluate the Specific Use Case:

   • Clearly understand how Firestore is being used in your deployed solution.
   • Determine if the functionality provided by Firestore is essential or if it can be replaced by CloudSQL or another suitable database.

2. Consult Apigee Support:

   • Reach out to Apigee support for expert guidance on modifying the deployment.
   • They can provide specific instructions and potential workarounds based on your use case.

3. Consider a New Deployment with Modified Configuration:

   • If significant modifications are required, creating a new deployment with the desired configuration might be a more practical approach.
   • This allows you to tailor the solution to your exact needs without affecting the existing deployment.

Potential Challenges and Considerations:

• Data Migration: If you're switching from Firestore to CloudSQL, you'll need to carefully migrate your data.
• Configuration Changes: Modifying the configuration of the deployed solution requires careful attention to avoid breaking the functionality.
• Security Implications: Any changes to the database configuration should be done with security in mind.

Remember: While it's possible to make modifications to a deployed Cloud Marketplace solution, it's crucial to approach the process with caution and seek expert advice when necessary.

I hope this provides a clearer understanding of the limitations and potential approaches.

Thanks!

[kedarkhaire]

Please also check the document https://cloud.google.com/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize

[VinP]

Many thanks @kedarkhaire