Timeline for Making data available for multiple microservices
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2022 at 22:48 | answer | added | Ewan | timeline score: 1 | |
| May 6, 2022 at 22:28 | answer | added | Wim Ombelets | timeline score: 2 | |
| May 6, 2022 at 21:21 | comment | added | J.R. | It sounds like that your intended solution is either not scalable or you are not expecting "too many" users when considering to fetch "all users" for the leaderboard. I assume no one is looking at the entire leaderboard all the time and it does not need to be kept up-to-date in real-time? A solution may be to go with option number 2 but design the service communications to fetch users in batches on demand, while maintaining a local cache and limiting cache updates to some reasonable rate. | |
| May 6, 2022 at 18:48 | comment | added | Robert Harvey | Seems like you've done the right thing, which is to evaluate the pros and cons of each approach. The "correct" way is the one that most effectively meets your project's functional and non-functional requirements. | |
| May 6, 2022 at 17:50 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 18 characters in body
|
| S May 6, 2022 at 17:21 | review | First questions | |||
| May 6, 2022 at 22:50 | |||||
| S May 6, 2022 at 17:21 | history | asked | Luis Novo | CC BY-SA 4.0 |