最简单的安全 Android 服务器后端
我有一个 Android 游戏，我希望它能够针对服务器后端的每个用户存储数据（例如高分）。
这是一份极其苛刻的要求清单！任何解决方案都不可能满足所有这些需求，因此我对它们进行了更改/优先排序：
- 最少/非常简单的服务器和客户端代码
- 免费/便宜
- 自动可扩展且无需/很少进行服务器维护
- 使用最少的代码尽可能安全
- 无缝 - 无需用户操作需要授权/选择
我所知道的有关 Parse 的任何内容，这似乎是最简单的选择，但我担心未来的成本并且更喜欢更多的控制，所以我想要一些替代方案。
尽管 AWS 可以相当轻松且良好地处理安全匿名身份验证，但它似乎付出了很大的努力。
如果有一种简单的方法来保护请求而不需要用户登录或授权应用程序引擎，那么应用程序引擎会很棒。
所以...我想要 Parse 的无缝性、AWS 的安全性以及 App Engine 的自动扩展能力。还有 Parse 的易用性/编码。手指交叉。 ：）
谢谢
I have an Android game and I want it to store data - say a high score for example - against each user on a server backend.
Here's a list of outrageously demanding requirements! It's unlikely any solution can meet all these demands, so I've changed/prioritised them:
- Minimum/very easy server and client code
- Free/cheap
- Automatically scalable and no/little server maintenance
- As secure as possible with minimum code
- Seamless - no user action required to authorise/choose anything
I know about Parse, and that seems the easiest option but I'm concerned about the future cost and would prefer more control so I'd like some alternatives.
AWS seems a lot of effort, although it handles secure anonymous authentication fairly easily and well.
App Engine would be great if there was an easy way to secure requests without requiring the user to login or authorise app engine.
So... I want the seamlessness of Parse, the security of AWS, and the auto-scaling of App Engine. Also the ease of use/coding of Parse. Fingers Crossed. :)
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我的建议：使用 Parse，但在模型中创建足够的抽象/封装，以便将 Parse 替换为另一个服务不会那么痛苦。但说真的，我不认为 Parse 会变得昂贵（甚至不是免费），直到您的应用程序出现非常高的需求。此外，Parse 人员似乎非常致力于开放性：您可以将数据导出为 CSV，并且他们有 REST API，因此您编写的任何类型的程序都可以访问数据。
如果您决定自己开发，我建议您使用 Heroku 创建 Rails 后端。 Piggyback SSL 是免费的，HTTP Basic Auth 在 Rails 中非常简单，整个堆栈将与您想要使用的任何数据库很好地配合（我假设 NoSQL，因为您需要灵活性）。
My advice: use Parse, but create enough abstraction/encapsulation in your models so that swapping Parse out for another service won't be so painful. But seriously, I don't think Parse will get expensive (or even not-free) until your app is seeing very high demand. Furthermore, the Parse guys seems pretty committed to openness: you can export your data as a CSV and they have a REST API so any type of program you write can access the data.
If you're determined to roll your own, I'd recommend creating a Rails back-end with Heroku. Piggyback SSL is free, HTTP Basic Auth is really easy in Rails, and the entire stack will play nicely with whatever db you'd want to use (I'm assuming NoSQL since you want flexibility).
任何支持 SSL 和数据库的 PaaS 都可以。估计您的流量、数据存储和处理需求，然后选择一个足够便宜的开始。 App Engine 即将结束测试版，定价模型也将发生变化，因此如果您想要自动缩放，则必须付费。
“安全匿名身份验证”到底是什么？AWS 如何支持它？
Any PaaS that supports SSL and a dataabse will probably do. Estimate your traffic, data storage and processing needs and pick one that is cheap enough to get started. App Engine is going out of beta soon, and the pricing model will be changed, so if you want autoscaling you'll have to pay for it.
What exactly is 'secure anonymous authentication' and how does AWS support it?