处理拆分应用程序的策略
为了应对最近的增长，我们的应用程序已分为两组独立的基础设施。我们大约一半的客户在集合 1 上，另一半在集合 2 上。
两个集合都有不同的 URL（api1.ourdomain.com 和 api2.ourdomain.com）。
问题是客户不小心输入了错误的网址，然后想知道为什么会收到错误消息。
除了用户教育之外，还有其他策略来处理这种混乱吗？
是否可以将请求重定向到正确的端点？
谢谢。
To deal with recent growth our application has been split across two sets of separate infrastructure. Approximately half of our customers are on set 1 and the other half are on set 2.
Both sets have different urls (api1.ourdomain.com and api2.ourdomain.com).
Problem is clients accidentally putt the wrong url and then wonder why they get error messages.
Other then user education any other strategies for dealing with this mess?
Is it possible to redirect requests to the correct endpoint?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为您的问题不够详细，无法提供有意义的反馈。显然有几个因素可以很容易地促成推荐。
您的应用程序是否使用用户配置文件（或类似的构造）？如果是这样，您可能会考虑在每个用户的配置文件中关联一个主 URI，并在应用程序中包含逻辑来询问每个请求的配置文件，并在用户访问错误的 URI 时进行重定向。
这是授权问题吗？如果是这样，您可能会考虑包含一些基本的授权路由，以提供具有正确 URL 的自定义 403 页面。
如果您能提供更多详细信息，我想我们会更有帮助。
I don't think your question is detailed enough to provide meaningful feedback. There are obviously several factors that could easily contribute to a recommendation.
Does your application make use of user profiles (or a similar construct)? If so you might consider associating a primary URI for each user in their profile and include logic in your application to interrogate the profile for each request and redirect if a user goes to the wrong URI.
Is this an authorization issue? If so you might consider including some basic authorization routing that provides a custom 403 page with the proper URL.
If you could provide additional detail I think we could be more helpful.