简体繁体 English

通过 API 拉取数据的更好方法？

[英]Better Way to Pull Data Through API?

原文 2019-04-26 17:35:58 8 2 java/ sql/ json/ api/ web-applications

So I'm trying to design a web app that requires a good amount of data (10,000 rows).所以我正在尝试设计一个需要大量数据（10,000 行）的网络应用程序。 This amount, however, will grow exponentially over time.然而，随着时间的推移，这个数量将呈指数增长。 Maybe into hundreds of thousands of rows.也许成几十万行。 I want to describe two methodologies of how to pull in and present the data and get recommendations on which method would be faster overall.我想描述两种关于如何提取和呈现数据并获得关于哪种方法总体上更快的建议的方法。 Also, the people using the webapplication are local to the servers (very low, if any latency)此外，使用 web 应用程序的人在服务器本地（非常低，如果有延迟）

The first method:第一种方法：

Make one call to an API which returns all 10,000 rows of data on the initial application load (pulls all the required data using 1 large stored procedure call)对 API 进行一次调用，该 API 在初始应用程序加载时返回所有 10,000 行数据（使用 1 个大型存储过程调用提取所有所需数据）
Count through this data using JavaScript looping and sort it into 20 categories based on certain criteria (Also JS)使用 JavaScript 循环计算这些数据，并根据特定标准将其分为 20 个类别（还有 JS）
When a user clicks on one of the counts displayed, they get a page that lists all the data rows pulled that matched that particular category.当用户单击显示的计数之一时，他们会看到一个页面，其中列出了与该特定类别匹配的所有数据行。 (This step would be extremely fast because all rows were preloaded) （此步骤将非常快，因为所有行都已预加载）

Second Method:第二种方法：

Make an initial API call that returns only the counts for each category based on certain criteria (Counts data on sql server instead of JS) When user clicks on count, makes another API call to return only the rows and data associated with that particular category (this means a separate SP for each category)进行初始 API 调用，根据特定条件仅返回每个类别的计数（在 sql server 上而不是 JS 上计数数据）当用户单击计数时，进行另一个 API 调用以仅返回与该特定类别关联的行和数据（这意味着每个类别都有一个单独的 SP）
This means, every time they click a category, a new API call will execute but the dataload will be much smaller这意味着，每次他们点击一个类别时，都会执行一个新的 API 调用，但数据负载会小得多

My hangup on this - The first method requires only 1 API call, but counts all the data in JavaScript and all at once, meaning even if you don't need some of the data, it is all loaded.我的挂断 - 第一种方法只需要 1 个 API 调用，但会一次性计算 JavaScript 中的所有数据，这意味着即使您不需要某些数据，它也会全部加载。

The second method requires multiple API calls, but counts all the data on the SQL Server and only returns the data that you need on demand.第二种方法需要多次调用API，但是统计SQL Server上的所有数据，只返回自己需要的数据。 Will making a lot of separate API calls instead of 1 large API call slow things down?进行大量单独的 API 调用而不是 1 个大型 API 调用会减慢速度吗？

2 个解决方案

Imho you shold go with the second option.恕我直言，你应该选择第二个选项。 i would not see a problem wrt to performance.我不会看到性能问题。 Counting based on category will be fast and the next calls will be smaller as amount returned and processed by the server.基于类别的计数将很快，并且随着服务器返回和处理的数量，下一次调用将更小。

It's important to consider how many times you would need to retrieve this data in a day.重要的是要考虑一天内需要检索这些数据的次数。 If its a handful--like 500 times max--option 1 is fine.如果它是少数——比如最大 500 倍——选项 1 就可以了。 If the number of calls is significantly higher than that, option 2 would be better.如果调用次数明显高于此值，则选项 2 会更好。 You would just retrieve a subset as needed.您只需根据需要检索一个子集。