基于SaaS的在线门户架构 [英] Architecture for SaaS based online portal
问题描述
我们正在计划基于SaaS模式准备一个产品在线服装店。
We are planning to prepare a product "online clothing store" based on SaaS model.
不同的布料商必须向我们的门户注册。他们将获得Web界面来管理自己的衣服目录。
Different cloth vendors shall register to our portal. They will get web interface to manage own catalog of clothes.
当最终用户向系统注册时，他们可以看到不同供应商的不同目录。
当然可以在可用的产品上进行标准搜索，过滤，排序等。
选择后，他们将订购商品。相应的供应商应从他的目录中选择这些项目的订单。
When end user register with the system, they can see different catalogs of different vendor. Of course they can do standard search, filter, sort etc on available products. After selection, they will order the items. Respective vendor shall get order of those items, which is selected from his catalog.
最后，我们将需要管理面板和客户CRM。它将保留所有客户的记录和数据。我们需要产生关于客户的分析。我们将记录客户如何响应不同供应商的不同产品，并根据研究行为。
At our end, we shall require administration panel and also customer CRM. It will keep records and data for all customers. We shall need to generate analytic about the customers. We shall record how customers are responding to different products of different vendors and according to study the behavior.
它需要是非常可扩展的产品。即使百万的供应商想加入，应该支持它。
It requires to be very scalable product. Tomorrow even if million of vendor wants to join, it should support it.
我需要关于架构和整体设计的建议：
I need advice about the architecture and overall design:
- 应该使用什么架构？
- 任何参考系统可供考虑使用？
- 设计模式，我们可以在实现时考虑？
- 任何数据库设计的建议？
- 如何确保门户网站可扩展？ li>
- What architecture should be used?
- Any reference system is available for consideration?
- Any specific design pattern, we can consider while implementing it?
- Any recommendation for database design?
- How to make sure that portal will be scalable?
推荐答案
构建SAAS软件涉及到一些事情。
There are a few things involved to build a SAAS software.
应该使用什么架构？
What architecture should be used?
SOA / Microservices架构是强烈推荐。松散耦合，聚集和负载平衡。
A SOA/Microservices architecture is highly recommended. Loosely coupled, clustered and load balanced.
任何参考系统可供考虑使用？
Any reference system is available for consideration?
Google搜索可能会提供示例。
A google search could probably give examples.
任何具体的设计模式，我们可以考虑一下实现它？
Any specific design pattern, we can consider while implementing it?
没有单一的设计模式。坚持SOA和高度分离的子系统将有所帮助。考虑微服务，并根据您的要求评估其优缺点。看看
SaaS成熟度模型级别4中的租户负载平衡器说明
There is no single design pattern. Sticking to SOA and highly decoupled subsystems will help. Consider microservices and evaluate its pros and cons for your requirement. Take a look at Explanation of Tenant Load Balancer in SaaS maturity model level 4
数据库设计的任何建议？
Any recommendation for database design?
有些数据库模型可以帮助SAAS软件。看看面向云上的企业Web（RIA）应用程序的数据库架构（单个数据库与客户端特定的数据库）
There are some DB models that help SAAS softwares. Take a look at Databse architecture (single db vs client specific db) for Building Enterprise Web (RIA) application on cloud
如何确保该门户将是可扩展的？
How to make sure that portal will be scalable?
理想情况下，可以根据需要添加新实例的云部署。即使不在云端，也需要一种类似于路由/负载平衡的设置，即可以添加新实例，这与私有云类似。
Ideally, a cloud deployment where new instances can be added on demand. Even if not on a cloud, a similar setup with routing/load balancing enabled where new instances can be added is required, similar to a private cloud.
这篇关于基于SaaS的在线门户架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
