从托管 (saas) 迁移到单独部署时要考虑什么
我工作的公司销售托管（即软件即服务）软件系统。 现在有人问我们是否可以为潜在客户提供软件的本地安装，这与人们转向托管模型的其他地方似乎正在发生的情况相反。 问题是我们在提供此服务时应该考虑什么以及可能出现的问题，我们在办公室进行了一些讨论，但我想我应该将其发布给更广泛的社区。 我们的应用程序需要安装 sql server、一些其他依赖项（即 tomcat）并安装一些 Windows 服务。 我想我们的系统需要专用（可能是虚拟）机器。
The company I work for sells a hosted (ie software as a service) software system. We've now been asked if we can provide a local install of the software for a potential customer, sort of the reverse of what seems to be happening else where with people moving towards the hosted model. The question is what we should consider in providing this and where the likely gotchas could be, we've had some discussion in the office but I thought I'd put it out to a wider community. Our app requires a sql server install, some other dependencies (ie tomcat) and installs a few windows services. I'd presume we'll require dedicated (possibly virtual) machines for our system.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当您放弃 SaaS 时，支持将变得更加复杂。 尽管您现在谈论的是一名客户，但您应该考虑这些问题对于 5、10 或 50 名客户的影响如何。
客户会自己进行备份吗？ 如果出现问题，他们必须重新安装您的软件并恢复备份，他们可以自己做还是您需要去现场？ 如果您确实需要进行现场访问，您的响应时间是多少？
他们有数据库的管理员访问权限吗？ 如果没有，他们能否有效地管理备份？ 如果是这样，当他们开始摆弄并添加自己的“性能增强”时会发生什么？
新版本和升级：通过 SaaS，您可以在需要时部署升级，每个人都将立即开始使用新版本。 如果你破坏了某些东西，这很糟糕，但至少你知道自己的立场。 通过单独部署，所有客户都将在不同时间进行升级，并且您必须开始支持软件的多个版本。
客户会自行安装更新还是您会远程安装？ 您的部署过程有多复杂 - 单击还是 10 个步骤？
您的软件将在什么硬件上运行？ 专用服务器还是使用了 5 年且也运行 Exchange 的台式机？ 如果您的软件运行报告，但一小时内没有人收到电子邮件，这会是您的错吗？
这些都不是无法克服的问题。 每个销售打包软件的人都必须处理这些问题，但当您自己运行服务时，您不必担心这些问题。 对于单个客户来说，可能不值得为此带来额外的麻烦。
您还可以考虑沿着设备路线发展，就像谷歌对其搜索设备所做的那样。 您向客户出售一台预装并配置了所有软件的服务器。 您可以完全远程访问该盒子，但他们只有有限的权限。 但他们的数据保留在现场，而不是存储在云端。 这可能是一个很好的折衷方法。
Support will get a lot more complicated when you move away from SaaS. Although you're talking about one customer now, you should consider how these issues will scale with 5, 10 or 50 customers.
Will the customer be doing their own backups? If things go wrong and they have to reinstall your software and restore their backups, will they be able to do it themselves or will you need to go onsite? If you do need to do a site visit, what will your response time be?
Will they have admin access to the database? If not, will they be able to manage backups effectively? If so, what happens when they start fiddling and adding their own "performance enhancements"?
New releases and upgrades: With SaaS you can deploy upgrades when you want, and everyone will start using the new version straight away. This sucks if you break something but at least you know where you stand. With individual deployments all customers will upgrade at different times and you'll have to start supporting multiple versions of your software.
Will the customer install updates themselves or will you do it remotely? How complex is your deployment procedure - single click or 10 step process?
What hardware will your software be running on? A dedicated server or a 5 year old desktop that's also running Exchange? If your software runs a report and no-one gets email for an hour, will that be your fault?
None of these are insurmountable problems. Everyone who sells packaged software has to deal with them, but they're things you don't have to worry about when you run the services yourself. It might not be worth the extra hassle for a single customer.
You could also look at going down the appliance route, like Google do with their search appliances. You sell the customer a server with all your software pre-installed and configured. You have full remote access to the box, but they only have limited rights. But their data stays onsite and not off in the cloud. This could be a good compromise approach.