Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

API Caching #42

Open
Lan2u opened this issue Jul 8, 2020 · 0 comments
Open

API Caching #42

Lan2u opened this issue Jul 8, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@Lan2u
Copy link
Member

Lan2u commented Jul 8, 2020

Is your feature request related to a problem? Please describe.
We don't do any caching of responses, this means every single request generates a call to at least 1 backend microservice and database.

Describe the solution you'd like
We should look into setting up a system for caching at the gateway with some benchmarking/testing done of various timeout / TTL values or mechanisms. This should hopefully reduce the number of messages that need to be sent internally and improve API response times.

This isn't a priority as the number of requests is expected to be extremely low but once the front-end starts to gain in complexity I can easily see an exponential increase in requests happening.
@Lan2u Lan2u added the enhancement New feature or request label Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lan2u