简体   繁体   English

服务网格和异步服务

[英]Service mesh and Async services

I am planning to introduce K8s/Istio into my infra. 我计划将K8s / Istio引入我的基础设施。 Right now I have plenty of services which communicate with each other using RabbitMQ. 现在我有很多服务使用RabbitMQ相互通信。

Service mesh concept seems to assume all services should be synchronous. 服务网格概念似乎假设所有服务都应该是同步的。

I'd like to keep at least some of my services async and take advantage of Mutual TLS Authentication which istio provides and also aggregated monitoring. 我想至少保留一些我的服务异步,并利用istio提供的Mutual TLS身份验证以及聚合监控。

Is there any tools/methods which can help me to streamline management of both Sync and Async services? 是否有任何工具/方法可以帮助我简化Sync和Async服务的管理?

Thanks, 谢谢,

Please note that Istio can control non-HTTP protocols on top of TCP, including providing Mutual TLS Authentication. 请注意,Istio可以在TCP之上控制非HTTP协议,包括提供相互TLS身份验证。 See this example of mTLS for HTTPS (treated as opaque TCP) - https://preliminary.istio.io/docs/tasks/security/https-overlay.html . 请参阅此mTLS for HTTPS示例(视为opaque TCP) - https://prelimin.istio.io/docs/tasks/security/https-overlay.html

I am not familiar with AMQP, but since it is a protocol on top TCP , it should be possible to control it by Istio as opaque TCP. 我不熟悉AMQP,但由于它是顶级TCP上的协议 ,因此应该可以通过Istio将其控制为不透明的TCP。

Apparently there is WIP to add Async (Event driven) messaging to Envoy Proxy through Kafka filter: https://github.com/envoyproxy/envoy/issues/2852 显然有WIP通过Kafka过滤器向Envoy代理添加异步(事件驱动)消息: https//github.com/envoyproxy/envoy/issues/2852

Also good summary on using a Service Mesh for Event-Driven Messaging here: https://www.infoq.com/articles/service-mesh-event-driven-messaging 此处还有关于使用Service Mesh进行事件驱动的消息传递的很好的总结: https//www.infoq.com/articles/service-mesh-event-driven-messaging

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

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