适用于聊天应用程序的AWS AppSync [英] AWS AppSync for chatting application

问题描述

我正在尝试使用AppSync聊天应用程序.我能够复制AWS教程( https://aws.amazon.com/blogs/mobile/building-a-serverless-real-time-chat-application-with-aws-appsync/)

I'm trying to use AppSync for chatting application. I'm able to reproduce the AWS tutorial (https://aws.amazon.com/blogs/mobile/building-a-serverless-real-time-chat-application-with-aws-appsync/)

但是，我仍然不确定AppSync是否可以处理用于聊天应用程序的生产环境.会因为DynamoDB部分而昂贵吗?

However, I'm still not sure if AppSync can handle a production environment for chatting application. Will it be expensive because of the DynamoDB part?

此外，如果我订阅每个对话，如果我希望每个用户进行1000个对话，那么前端用户的性能会有问题吗?

Moreover, if I'm subscribing each conversation, will there be a performance issues for the users in the front-end if I have like 1000 conversations / user?

推荐答案

使用AppSync和DynamoDB无疑将适合处理1000个会话的生产环境，并且能够进一步扩展.但是，AppSync和DynamoDB的成本可能会更高.

Using AppSync and DynamoDB no doubt will suit a production environment handling 1000 conversations and is able to scale much further. However, the cost can get higher both for AppSync and DynamoDB at scale.

尽管如此，但由于开发和管理工作是全托管服务，因此在考虑总拥有成本时要进行权衡，这要少得多.

While saying that, its a tradeoff when considering the total cost of ownership since the development and management effort is significantly less since these are fully managed services.

与您要比较的技术相比，这也是主观考虑.因此，我建议做一个粗略的容量规划，并提出一个估算值，以与其他几种技术进行比较(例如，即使在AWS内；您也可以考虑使用AWS IOT Websockets，AWS Message MQ来构建实时聊天应用程序)

It is also subjective considering, against what technology you are comparing with. So what I would suggest is to do a rough capacity planning and come up with an estimation to compare against few other technologies (Even within AWS, e.g; You can also consider AWS IOT Websockets, AWS Message MQ to build real-time chat applications).

这篇关于适用于聊天应用程序的AWS AppSync的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！