多领域站点设计决策
我正在开发一个项目，其领域对我的母语来说是有意义的。 所以我购买了第二个英文域名供全球使用。
我的问题是，我应该如何构建我的网站？
- 两个不同的项目还是一个具有本地化支持的项目？
- 两个不同的数据库还是共享数据库？
我的目标是什么？
- 不想在本地站点中显示英文内容，反之亦然
- 我想轻松更新站点
如果您建议我使用共享数据库，您能向我描述一下数据库的设计原理吗？
谢谢。
i am developing a project that its domain is meaningful in my native language. So i bought a second English domain for global usage.
My question is, how should i construct my site?
- Two different projects or one project with localization support?
- Two different databases or shared database?
What is my goal?
- Dont want to show English content in native site, vice versa
- I want to easily update site
If you suggest me to use shared database, could you please describe me design principle of database?
Thank You.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
通常，对于应用程序代码，您最好不要出于任何原因（包括语言）分叉。 您需要注意一些快速的事情；
这更多地取决于您持有的数据，例如，
但是，
如果您发现以下情况属实，则
您可能倾向于两个独立的数据库，这将为您带来扩展方面的优势（尽管它不是一个）。银弹），只要数据库之间的模式相同，您可能会发现它并不太繁重。
另一种选择是识别共享资源并将其拆分到另一个存储库中（例如用户登录等......）。 这可以让您两全其美，但当然这是一个更复杂的设计。
请记住，所有这些都可以在事情变得更困难之后添加。 有时，进入市场比尝试预先解决所有问题更重要。
祝你好运！
Typically for application code you ideally want to not fork for any reason including language. There are some quick things you need to watch out for;
As for the database this depends more on the data your holding, for example if;
You might want to have one database.
However if you find the following are true;
You might lean towards two separate databases. This will give you an advantage in scaling (though its not a silver bullet) and as long as the schemas are identical across the databases you will likely find that it's not too onerous.
One other option is to identify shared resources and split them into another repository (think user logins etc...). This can get you the best of both worlds but of course is a more complex design.
Remember all of this can be added after the fact it just becomes harder. Sometimes it's more important to get to market than it is to try and solve all your problems up front.
Good Luck!
我不太确定什么对你有用，但我认为本地化支持会很好，如果你有一个共享数据库，你就不需要支持不同的数据库，也不需要添加额外的数据库任何时候你需要添加一种新语言，并且考虑应用程序，如果你想要另一种语言只是将其添加到你的配置中，而不是创建另一个项目只是为了添加它，那么会更容易。
I'm not quite sure what could work for you, but I think that localization support would it be nice, and if you have a shared database you won't need to support to different databases and you won't need to add an extra database anytime you need to add a new language, and thinking about the application it would be easier just to if you want another language just to add it to your configuration and not create another project just to add that.