cloudfoundry / cloudfoundry/uaa
read/write split in UAA
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 844
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 27
Description
UAA version : 78.0.2
We are deploying Cloud Foundry UAA on AWS ECS backed by an Aurora MySQL cluster with one writer and multiple reader instances.
Our question is regarding read/write traffic distribution:
Does UAA have built-in support for routing read queries to Aurora read replicas (using the cluster-ro endpoint) while ensuring write operations continue to go to the writer endpoint?
If not, what is the recommended best practice for using UAA with Aurora to take advantage of read replicas?
Any guidance on how to properly configure UAA with Aurora so that it efficiently utilizes the reader/writer setup would be very helpful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by checking UAA's database configuration and whether it supports separate Aurora writer and reader endpoints; done means documenting whether read/write splitting is supported and the recommended configuration for Aurora MySQL on AWS ECS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, mysql
- Domain
- backend, databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100