Use sidecar database proxy connector on pay for better performance
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
[RFC: High-Performance Multi-Container SQL Auth Proxy Sidecar with IAM Auth](https://github.com/bcgov/connect/discussions/5)
[Sample Code](https://github.com/bcgov/bcregistry-sre/tree/main/poc/db-sidecar)
[Deployed Google Cloud Platform](https://console.cloud.google.com/run/detail/northamerica-northeast1/flask-fast-iam-service)
Execute it here:
curl -s -H "Authorization: Bearer $(gcloud auth print-identity-token)" https://flask-fast-iam-service-366678529892.northamerica-northeast1.run.app/health
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked RFC and the sample implementation in bcregistry-sre/poc/db-sidecar, then inspect the deployed Google Cloud Platform Flask service. Compare the current database connection approach with the sidecar connector and use the provided curl health check to verify the deployed service remains healthy after the integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, gcp, postgres
- Domain
- backend, cloud, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100