对于以 Stack Exchange 或 Basecamp 的方式启动白标系统有一些疑问

发布于 2024-08-17 01:17:45 字数 861 浏览 4 评论 0原文

嘿大家好,我正在开发一个项目,我不会详细介绍,但它将由我编程/设计,并将允许客户注册自己的实例,他们将能够自定义它。把它想象成类似 phpbb 的东西,它们是由我托管的一堆,客户将每月支付费用,并将获得他们项目版本的子域。

我正在尝试决定如何在服务器端进行设置并查看以下选项:

1)将所有内容托管在一台或两台服务器上

优点

  • 易于推出更改,因为所有内容都在同一台服务器上 让子域
  • 指向同一位置将是一件轻而易举的事,因为源代码只有一个位置,并且只有一个数据库
  • 用户将能够对所有客户端使用全局登录,因为只有一个 users

缺点

  • 扩展很快就会变得很麻烦,因为所有流量都在一个盒子上
  • 数据库查询会因为行数高而变慢(大多数情况下都会有一个 client_id 字段ID 数据属于哪个子域)

2) 利用 EC2、Rackspace Cloud 或类似的东西

优点

  • 可以像梦想一样扩展

缺点

  • 我只是没有平台经验,无法预见所有问题(是的,我知道,蹩脚的借口)
  • 不确定我如何能够向所有实例推出新版本
  • 不确定我是否可以以某种方式进行设置,以便客户一旦付款,他们就会立即设置好实例 不知道
  • 如何实现全局登录系统(尽管 37signals 似乎可以做到)

似乎最好的选择是云式的东西,唯一真正的问题是我缺乏经验。

有没有人推出过这样的东西?你做了什么?还有什么问题是我没有考虑到的吗?

Hey all so I am working on a project and I won't get into the details but it will be programmed/designed by me and will allow customers to sign up for their own instance of it where they will be able to customize it. Think of it as something along the lines of phpbb where they are a bunch of them being hosted by me that clients will pay a monthly fee for and will get a subdomain for their version of the project.

I am trying to decide how I am going to set this up on the server side and see these options:

1) Host everything on one or two servers

Pros

  • Easy to push out changes since everything is on the same box
  • Getting the subdomains to point to the same place will be a snap since there will only be one place that the source code lives and only one database
  • Users will be able to use a global login for all clients since because there is only one users table

Cons

  • Scaling will get hairy quickly since all the traffic will be on a single box
  • Database queries will be slow because of high row counts (there would be a client_id field for most things to ID which data belongs on which subdomain)

2) Take advantage of EC2, Rackspace Cloud or something similar

Pros

  • Scales like a dream

Cons

  • I just don't have the experience with the platform to be able to foresee all issues (yes I know, lame excuse)
  • Unsure how I would be able to push out new versions to all instances
  • Unsure if I could somehow set it up so that as soon as a client paid they would immediately have their instance set up and good to go
  • Don't know how I could implement a global login system (although 37signals seem to do it)

It seems like the best option is something cloud-ish and the only real issue is my lack of experience.

Has anyone ever launched something like this? What did you do? Any problems I'm not thinking about?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

烟雨凡馨 2024-08-24 01:17:45

只是一个快速数据点来帮助您做出决定...Amazon 限制每个 EC2 实例只能使用一个 IP 地址。如果您需要拥有多个白标签域名和 DNS,则需要为每个白标签创建一个新实例。

Just a quick data point to help you decide... Amazon restricts you to one IP address per EC2 instance. If you need to have multiple white label domain names and DNS, you'll need a new instance for each white label.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文