简体   繁体   English

多个SOA / API网关以满足内部和外部客户

[英]multiple soa/api gateways to satisfy internal and external customers

I have come across API and Service architectures where API/Svc gateway is positioned in DMZ for authorization/authentication of external(not employees) consumers. 我遇到过API和服务体系结构,其中API / Svc网关位于DMZ中,用于外部(非员工)使用者的授权/身份验证。 But, in my case, we have internal consumers also. 但是,就我而言,我们也有内部消费者。 The internal consumers are behind an intranet firewall that isolates them from DMZ. 内部使用者位于将其与DMZ隔离的Intranet防火墙后面。 My question is do i need to deploy a separate instance of API/Svc gateway for internal users for authentication/authorization that is within intranet or should internal api access have to go through the intranet firewall to DMZ and back into the intranet? 我的问题是,我是否需要在内部网中为内部用户部署一个单独的API / Svc网关实例以进行身份​​验证/授权,还是内部api访问是否必须通过内部网防火墙到达DMZ并返回内部网?

That depends on the gateway architecture. 这取决于网关的体系结构。 For example Tyk.io separates UI/Portal from the gateway nodes. 例如, Tyk.io将UI / Portal与网关节点分开。 If the UI components and the gateway nodes are separate then you can have a single portal but differentiated gateways to handle traffic from different sources. 如果UI组件和网关节点是分开的,那么您可以拥有一个门户,但是区分网关来处理来自不同来源的流量。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM