我正在考虑基于Spring Cloud的实现。 我有一个基于节点边缘服务的Eureka注册表。 Node服务使用Prana侧车来解析Eureka上的注册服务以及注册Node服务。 解决边缘服务的最佳做法是什么？ 我读到了Zuul。 这是正确的方法吗？ 或者它应该托管在像WSO2这样的网关上？ 此外，如果边缘服务是一个集群，那么常用的系统布局是什么？ 任何指针都将非常感激。
I am POCing a Spring Cloud based implementation. I have a Eureka registry with a Node based edge service. The Node service uses a Prana side car to resolve registered services on Eureka as well as register the Node service. What is the best practice for resolving the edge service? I read about Zuul. Is that the right approach? Or should it be hosted on a gateway like WSO2? Also, if the edge services are a cluster then what is the system layout that is commonly used? Any pointers would be greatly appreciated.
最满意答案
这取决于您的实际需求。 如果您需要对路由，负载均衡，过滤器逻辑等进行大量控制，或者您正在运行自己的堆栈和/或您无法访问动态负载均衡器，我建议您使用Zuul。
我们当前正在ELB上的AWS上运行多个Zuul实例，它们以循环方式调用，并且请求根据众多因素（元数据，路径，变量）路由到相应的服务。 到目前为止，我们还没有遇到任何性能问题。
It depends on your actual needs. I recommend using Zuul on your edge if you need a lot of control over your routing, loadbalance, filter logic etc or you are running your own stack and/or you don't have access to dynamic loadbalancers.
We are currently running multiple Zuul instances on AWS behind ELB, they are invoked in a round robin fashion and the requests are routed to the appropriate service based on numerous factors (metadata, path, variables). We haven't had any issues with performance so far.
更多推荐
发布评论