Comments (3)
Unsure of the thought around strategy, but in some projects, we tend to make a significant number of calls to get these settings. Depending on what is being stored for these settings, it may make sense to store them in application state, local storage or cached on the server. Eliminating the potential number of requests and/or database hits as much as possible while not allowing the data to get too stale.
from andculturecode.dotnetreact.boilerplate.
Agreed that we do tend to call settings, and honestly other shared tables, too often. Developers should take caution and limit their reading from the DB (or other external sources) in whatever ways best suits their use case. That said, it is risky and error prone from a user experience perspective to just have the settings code do caching out-of-the-box by the boilerplate. While I wish we could have a one-size-fits-all performance tuned conductor for all use cases out of the box, unfortunately the "age" and strategy for caching can vary by each individual setting itself.
In terms of where to cache, efforts to cache on the server should be first objective. Leaving that choice to the frontend client isn't enough. Even if we are the only ones consuming the API.
from andculturecode.dotnetreact.boilerplate.
Thanks for the reply @wintondeshong! I just wanted to make sure it was noted!
from andculturecode.dotnetreact.boilerplate.
Related Issues (20)
- Authentication and Authorization Strategy HOT 1
- Investigate Improvements to Logging
- Extract app#getCookie and app#hasCookie
- Extract AuthenticationSchemes to Core HOT 1
- Rename default branch from "master" to "main". HOT 1
- Add documentation re: migration flattening and base migration class.
- Authentication defaults
- Add `.npmrc` file to make npm always use exact versions HOT 3
- Port 'Frontend Performance Profiling' documentation
- Upgrade to React v18 HOT 1
- Add Repository.FindAll groupBy related overloads implementation HOT 1
- Upgrade to Cypress v6
- Upgrade to latest AndcultureCode JS Core, React packages
- Upgrade to .NET 5 HOT 1
- Run SQL Server integration tests in CI Build
- Upgrade to .NET 6
- Build Notifications
- Update Validator Tests
- Update React Boilerplate
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from andculturecode.dotnetreact.boilerplate.