blocks|key|4813752|text|如果您想要logIn您的用户，您必须调用远程DB对用户进行身份验证。在没有远程数据库的情况下，我看不出您在哪里能够做到这一点。否则，如果要显示所获得的数据，则只应查询DB，这是正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4813753|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you want to logIn your user you have to call the remote DB to authenticate the user. I do not see where you are able to do this without the remote db. 
Otherwise you are correct that you should only query the DB if you want to show the data you get.

blocks|key|4813767|text|这取决于场景，但我将使用选项2:首先，授予用户访问权限，并在需要时从后端检索数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4813768|想象一个非常简单的场景，用户登录查看他可以使用的产品列表(添加和删除)。该解决方案将由2个屏幕组成：|4813769|管理用户访问的登录屏幕。|unordered-list-item|4813770|产品列表屏幕用于处理产品|4813771|对我来说，在一个好的设计中，每个屏幕都有自己的响应性，每个屏幕应该只查询它将要管理的数据。|4813772|登录屏幕的责任只是执行登录，然后导航到产品屏幕。|4813773|产品屏幕责任是检索产品、显示产品并在用户结束编辑后存储它们。|4813774|如果登录屏幕查询产品数据以将其传递给产品屏幕，则需要将登录屏幕和产品数据耦合起来。|4813775|无论如何，如果您有一组静态数据可供多个屏幕使用(例如，产品类别)，则可以在第一次需要时查询它们，并将它们存储在缓存中以供进一步访问。|4813776|另一种情况可能是，如果可能存在联系问题。在这种情况下，最好的解决方案是下载一组用户可以使用的数据，编辑这些数据，然后将它们上传到后端(考虑到可能的并发问题)。|4813777|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|13|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|14|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|15|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|V|$]]

It depends on the scenario, but I would go with option 2: First, the user is granted the access and you retrieve the data from your backend when needed.

Imagine a very simple scenario where the user logs in to see a list of products he can work with (add and remove). The solution would consist of 2 screens:

<ul>
<li>A login screen to manage user access</li>
<li>product list screen to work with products</li>
</ul>

For me, in a good design each screen has its own resposibility, and each screen should query only the data that it is going to manage.

<ul>
<li>The login screen responsibility would be only to perform the login and then navigate to the product screen.</li>
<li>The product screen responsibility would be retrieve the products, show them and store them when the user has ended the editings.</li>
</ul>

If your login screen queries the product data to pass it to the product screen, you are coupling the login screen and the product data.

Anyway, if you have a set of static data that can be used by several screens (for example product categories), you can query them the first time you need them and store them in a cache for further accesses.

Another scenario could be if there can be conectivity problems. In this case the best solution could be to download a set of data that the user can work with, edit them and them upload them to the backend (taking into account the possible concurrency issues).

When I make an app, I always wonder when is the best moment to load data from a remote database. 
If the app ask for a login screen, then:

<ol>
<li>Is it better to launch every data from remote DB at his time, and then use them in the app? This way, the app is much faster after the login screen (no more queries needed to retrive some data) </li>
<li>Is it better to load data only when we need to use them (for example, display some data from DB into the app). This way, the login is much faster, but the app can be slower than the first case. </li>
</ol>

What do you guys think?

Best practice : when to load data from remote DB

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我制作一个应用程序时，我总是想知道什么时候是从远程数据库加载数据的最佳时机。如果应用程序要求一个登录屏幕，那么：是否最好在他的时候启动来自远程DB的所有数据，然后在应用程序中使用这些数据？这样，应用程序在登录屏幕后会更快(不再需要查询来检索一些数据)。只有当我们需要使用数据时才加载数据更好(例如，将一些数据从DB显示...

问最佳实践:何时从远程DB加载数据
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问最佳实践:何时从远程DB加载数据EN