[英]Return large volumes of data in REST API
I am developing REST APIs for mobile apps; 我正在为移动应用程序开发REST API; we have a web app, which doesn't filter large volumes of meta data.
我们有一个网络应用程序,该应用程序不会过滤大量的元数据。 Apps are taking more time to parse these high volume of (2k records with 5 columns) metadata.
应用程序需要花费更多时间来解析大量的元数据(5列2k记录)。 What are the best ways to handle this scenario from both API & App perspective.
从API和应用程序角度来看,处理此场景的最佳方法是什么。 API options are preferred..
首选API选项。
App devs are asking to return database (sql lite, etc) by combining all the metadata routes and initial sync into a single route.. I am not finding much pointer around this.. is this a practice in industry? 应用开发人员要求通过将所有元数据路由和初始同步合并到单个路由中来返回数据库(sql lite等)。我在这方面找不到太多的指针。.这在行业中是一种惯例吗?
You can think of using asynchronous streaming to send large data to front end and change the client to consume the stream 您可以考虑使用异步流将大型数据发送到前端并更改客户端以使用流
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.