解析每秒太贵请求。想要获得个人的AWS开发。建议吗？ [英] Parse request per second too expensive. Want to get personal AWS developed. Advice?

问题描述

我用了4时间学习目标C和斯威夫特，我仍然吮吸。但我能够完成我的MVP，我用解析，因为它是不是有我自己的服务器上建更容易。我已经准备好释放我的应用正式和我正在考虑迁移到AWS为更好的成本。

I spent 4 months learning Objective C and Swift and I still suck. But I was able to finish my MVP and I used Parse because it was easier than having my own server built. I am ready to release my app "officially" and I am thinking about migrating to AWS for better cost.

下面是我的应用程序的规格。该应用程序在您登录后有5个总页数和3主页的链接：

Here are my app specs. The app has 5 total pages and 3 main pages after you log in:

1. 在注册 - 我们只要求用户插入名称推送通知
2. 然后，他们输入自己的号码并等待来自Twilio验证code
文本
3. 获取设备中的联系人。发现谁拥有从通讯录应用程序的用户，并将其导入到应用程序的联系人
4. 发送文字，照片，链接到联系人（只派了通信从用户到用户）
5. 在接收文字图片链接（仅限：收到COMM从用户到用户

我们将需要存储姓名，电话号码，唯一ID，twillo密码，短信和图片服务器上。

We will need to store name, phone number, Unique ID, twillo password, text message and images on server.

这将是容易克隆解析REST API和并行处理？和云文件存储迁移到AWS？

Will it be easy to clone Parse rest api and parallel processing? And migrate cloud file storage to AWS?

会不会是值得拥有这个自由职业者或者我应该付出的代价解析？

Will it be worth having this freelanced or should I just pay the Parse price?

我工作的一个非常酷的聊天服务，它不喜欢你的传统聊天应用程序。这个聊天程序只允许你发送消息，你在一个凉爽的方式回应消息。我用推送通知提醒用户，当他们有一个新的消息。

I am working on a very cool chat service, its not like your traditional chat app. This chat app only allows you to send messages and you respond to messages in a cool way. I used push notifications to alert users when they have a new message.

但在这个任何反馈将是惊人的！

But any feedback on this will be amazing!

推荐答案

作为的personnal的经验，我建议你跟上解析下去。

As a personnal experience, I would suggest you keep going with Parse.

我其实使用AWS服务同时处理所需的API函数和文件存储上运行的应用程序。

Im actually running an app using an AWS serve to handle both the required api functions and the file storage.

如果你足够好，以建立你自己的API，以取代什么，提供解析，然后你就可以走了，但如果你不这样做，你将不得不考虑支付您后端可以从头构建。 （$$$）

If you're good enough to build up your own API to replace what is offering parse, then you're good to go, but if you don't you will have to consider paying for you backend to be built from scratch. ($$$)

然后，您将需要获得一个弹性的自动气象站，将相应账单你TRAFIC。这可能是比使用解析根据您的需要/应用程序TRAFIC，但我会建议得到一些数据更便宜的，看它是否值得麻烦。

Then, you will require to get an elastic AWS that will bill you accordingly to trafic. This could be cheaper than using Parse depending on your needs / app trafic but I would suggest to get some data to see if it worth the trouble.

在最后，你需要有人来处理维修和后端的改进。是啊，你在后端将需要所以如果你需要你的应用程序，以发展工作。

In the end, you will need someone to handle maintenance and backend improvements. Yeah, you're backend will need so work if you need your app to evolve.

解析将提供一切从灵活的API，存储，支持和维护。所有这一切都为下20个请求/秒免费。正如所说瑞安，如果你爆这个限制，那么你有一个积极的问题来解决。

Parse is providing everything from flexible api, storage, to support and maintenance. All of this for free under 20 requests / sec. As said by Ryan, if you burst this limit then you have a positive problem to fix.

此外，考虑有这样做的，你想建立每一个应用程序。不是再次，解析是一个好多个应用程序项目的解决方案。

In addition, consider having to do this for every app you want to build. Than again, Parse is good a solution for multiple app projects.

这篇关于解析每秒太贵请求。想要获得个人的AWS开发。建议吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！