The world of BAAS, or MBAAS, was shocked the past week with the announcement made by Parse on it’s site:

上周，Parse在其网站上发布的公告震惊了BAAS或MBAAS的世界：

Parse’s hosted services will be fully retired on January 28, 2017. We’re proud that we’ve been able to help so many of you build great mobile apps. Read more on this announcement and what this means for your app here. Thank you for using Parse

Parse的托管服务将于2017年1月28日完全停用。我们很自豪能够帮助如此多的人构建出色的移动应用程序，对此我们感到非常自豪。 在此处阅读有关此公告的更多信息以及这对您的应用意味着什么。 感谢您使用解析

The web was/is filled with people set on fire, running in circles discussing why this is happening, posible alternatives to move on to, and migration plans to other providers. Here I will present my approach to this discussion and a possible plan to move forward without too much hassle involved.

网络上充斥着被纵火的人们，围着圈子讨论了为什么会这样，继续前进的可能选择，以及向其他提供商的迁移计划。 在这里，我将介绍我的讨论方法，以及在不涉及太多麻烦的情况下前进的可能计划。

替代品 (The alternatives)

There are many alternatives to Parse and they are all good options. The main difference lies on the set of features and pricing conditions they offer. For this study, I will not be measuring the cost of migrating from Parse but If you have a big portion of your business logic there, you’ll probably have to also take this into account.

解析有很多替代方法，它们都是不错的选择。 主要区别在于它们提供的功能集和定价条件。 对于本研究，我不会衡量从Parse迁移的成本，但是如果您在那里有很大一部分业务逻辑，那么您可能还必须考虑到这一点。

火力基地 (Firebase)

This is the by default alternative to Parse. It has many of the features present in Parse but it adds some nice ones like: custom business logic, offline synchronisation management & in app purchase.

默认情况下，这是“解析”的替代方法。 它具有Parse中提供的许多功能，但增加了一些不错的功能，例如：自定义业务逻辑，离线同步管理和应用内购买。

Furthermore,  it provides means to observe changes on the remote database so you can distribute changes in your model in real time. This is a really valuable feature and combined with user management, schema-less data store and analytics made, Firebase is a great option if you need real time – multiple device communication.

此外，它提供了观察远程数据库上的更改的方法，因此您可以实时分布模型中的更改。 这是一项非常有价值的功能，并且与用户管理，无模式数据存储和分析功能相结合，如果您需要实时的多设备通信，Firebase是一个不错的选择。

Pricing:  from USD 5/m to USD 1499/m with a free plan alternative.

定价：从每月5美元到每月1499美元，并提供免费计划供您选择。

BaasBox (BaasBox)

This tool is in a different category where other options, such as Kinto from Mozilla, lie in. The product is open source so you can download and install it wherever you want. However, if you need a cloud service, like the one provided by Parse, then you will need to pull out your credit card. The pricing only depends on the amount of storage, which is indeed pretty convenient.

该工具位于其他类别中，例如Mozilla的Kinto等其他选项。该产品是开源的，因此您可以在任意位置下载并安装它。 但是，如果您需要像Parse提供的那样的云服务，那么您将需要取出信用卡。 定价仅取决于存储量，这确实非常方便。

The set of features is really small but it has what one expect to from an out of the box  solution; these are: user management (login, sign up, relation between users), data storage, push notifications, among others. It is a very good alternative for  people who only use a small fraction of what Parse provides, probably 80% of us.

这套功能确实很小，但是它具有开箱即用解决方案所期望的功能。 它们是：用户管理（登录，注册，用户之间的关系），数据存储，推送通知等。 对于只使用Parse提供的一小部分人（可能占我们的80％）的人们来说，这是一个很好的选择。

Pricing: USD 0 for solution // USD 28/m to USD 555/m for clouding.

定价：解决方案为0美元//云计算为28美元/ m至555美元/ m。

后端少 (BackendLess)

This is – by far – the most complete solution. It has all the features that Parse provides plus a guide to migrate your project from it to Backendless which is really handy.

到目前为止，这是最完整的解决方案。 它具有Parse提供的所有功能，以及将项目从项目迁移到Backendless的指南 ，这非常方便。

It has everything and more. One feature that seems not to be too common is the ability to plug your custom logic on the server side. I found it to be really useful when extending your business logic especially considering that if a service is lacking this feature it could mean having to move away form it completely.

它拥有一切，还有更多。 似乎不太常见的一项功能是可以将自定义逻辑插入服务器端。 我发现它在扩展您的业务逻辑时确实很有用，尤其是考虑到如果服务缺少此功能，则可能意味着必须完全放弃它。

Other really nice features I can’t find in other solutions are: version handling for your app (e.g. different database schema for each version), market place to extend your backend capabilities and code generation to bootstrap new projects.

我在其他解决方案中找不到的其他真正不错的功能是：应用程序的版本处理（例如，每个版本使用不同的数据库架构），扩展后端功能的市场以及引导新项目的代码生成。

Unfortunately, the pricing is  quite awful. You have three options: cloud free with functional limits, free standalone (deploy yourself) and fully cloud managed. The cloud free option has complex conditions so it can be hard to keep track of how much you are spending because of the number of conditions affecting the final price. Also the project is not open source so you don’t really have control over how/what is happening and can’t follow the evolution of the tools.

不幸的是， 价格相当糟糕。 您有三种选择：具有功能限制的免费云，免费独立（自行部署）和完全由云管理。 无云选项的条件很复杂，由于条件数量会影响最终价格，因此很难跟踪您正在花费多少。 此外，该项目不是开源的，因此您实际上无法控制发生的方式/发生的事情，也无法跟踪工具的发展。

对于所有替代品 (For all the alternatives)

I’m an iOS engineer, so my focus is on iOS. All I have to say is that none of the alternatives I saw so far has explicit Swift support. I saw some really active repos hosting iOS SDKs that are all pure Objective-C, but none are Swift.

我是一名iOS工程师，所以我的重点是iOS。 我要说的是，到目前为止，我所看到的所有替代方案都没有明确的Swift支持。 我看到了一些托管iOS SDK的真正活跃的仓库，它们都是纯Objective-C的，但是都不是Swift。

Don’t get me wrong I love the good old ObjC. It gave me years of fun and satisfaction, but times change and and Swift is a kind of standard now. I saw only few setup examples in Swift, and some of the alternatives don’t even provide it (I’m looking at you BASSBOX). I really only write Swift code now and it would be really nice to have an SDK in what the majority of the new apps are using, and are going to use for the all their existence.

不要误会我的意思，我喜欢古老的ObjC。 它给了我多年的乐趣和满足感，但是时代在变化，而Swift现在已经成为一种标准。 在Swift中，我只看到了几个设置示例，而有些替代示例甚至都没有提供它（我在看BASSBOX）。 我现在真的只写Swift代码，对于大多数新应用程序正在使用的东西以及将要使用的所有东西都拥有一个SDK真是太好了。

So for all of you MBAAS out there: provide native Swift SDK for iOS! Please

因此，对于所有人MBAAS：为iOS提供本机Swift SDK！ 请

建立自己的后端 (Build your own backend)

While all BAAS services can help you build your backend pretty quickly, they are not a one-size-fits-all solution. Sooner or later you will need customization options not offered by whatever service you’re using.

尽管所有BAAS服务都可以帮助您快速构建后端，但它们并不是万能的解决方案。 迟早您将需要使用的任何服务都无法提供的自定义选项。

It is true that getting started is probably much quicker (and cheaper) with BAAS services, as most basic cases have already been solved for you. However, as soon as you need to add specific business logic it may mean that whatever service you’re using is good no longer, thus, you end up having to migrate to another service or a custom built solution. In any case, this ends up being as, if not more, expensive than building your own software from the get go.

的确，BAAS服务的入门可能更快（且更便宜），因为大多数基本情况已为您解决。 但是，一旦您需要添加特定的业务逻辑，则可能意味着您所使用的任何服务都不再有效，因此，您最终不得不迁移到另一个服务或定制的解决方案。 无论如何，这最终要比一开始就构建自己的软件昂贵，甚至更多。

Building an API from scratch can sometimes seem like a daunting task, but in reality there’s a lot of code than can be reused to build a reliable API for your business. Frameworks like Django remove a lot of the hassle involved, leaving you to care about the logic involved, which in the end is what matters.

从头开始构建API有时似乎是一项艰巨的任务，但实际上，有很多代码无法重复使用以为您的企业构建可靠的API。 诸如Django之类的框架消除了很多麻烦，让您去关心其中涉及的逻辑，这最终才是最重要的。

A custom made API not only gives you total control over its behaviour, it also allows you to take care of other non-functional aspects, such as other software you depend on (e.g. DBMS), how it’s hosted and served, how data is backed up, etc. An interesting side effect of this is that you also control how your service scales and are not being limited by any 3rd party services.

定制的API不仅可以让您完全控制其行为，还可以让您处理其他非功能性方面，例如您依赖的其他软件（例如DBMS），如何托管和提供服务，如何备份数据等等。一个有趣的副作用是，您还可以控制服务的扩展方式，不受任何第三方服务的限制。

结论 (Conclusion)

翻译自: https://www.pybloggers.com/2016/02/parse-is-gone-now-what/