search

mosn / layotto

A fast and efficient cloud native application runtime
http://mosn.io/layotto/
Apache License 2.0
817 stars 168 forks source link

Q&A record #436

Open seeflood opened 2 years ago

seeflood commented 2 years ago

This issue is used to record Q&A so that we can improve documentation according to them, see https://github.com/mosn/layotto/issues/443

We have a test-driven documation improvement strategy:

If we can't answer a user question by just sending him/her a link, then we need to consider whether the answer should be written into a document.

Question lists:

New doc will be added in #435

seeflood commented 2 years ago

Q: 使用layotto是不是客户端代码需要重新实现，全部调用layotto提供的API ？ 多少正式的项目正在使用这种layotto？ A: 落地用户是改客户端sdk，改成调用 layotto；现在在搞无侵入方案

Q:这部分开源了吗，开源版服务器端支持那些中间件，客户端支持哪些？客户端无侵入支持哪些中间件 A:

  1. 已经落地的方案是：改各种中间件的java sdk，改成调用 layotto （比如把 xxx-MQ-sdk 内部逻辑改成调layotto pubsub API，但是对业务代码暴露的接口不变)，业务系统需要升级下sdk，业务代码不用改。

这部分没开源，因为没开源价值……因为是改内部中间件的 sdk，这些中间件本身没开源。

  1. 开源版服务器端支持那些中间件 每类 API 有支持的组件列表，https://mosn.io/layotto/#/zh/component_specs/sequencer/common 其中 state API、pubsub API 因为复用了 dapr 的组件，所有 dapr 组件都支持，dapr 有个组件支持列表， https://docs.dapr.io/zh-hans/reference/components-reference/supported-state-stores/

  2. 客户端支持哪些

目前有 .net java go 的layotto sdk，有个layotto-springboot刚合并 sdk在 https://github.com/layotto

  1. 关于无侵入方案：后面想把协议转换的事情放到layotto做、让用户接入layotto 时不用改客户端sdk，不过方案还在讨论，最近会写个 proposal

现在还没有现成的客户端无侵入 sdk，老系统 接入layotto 需要改原来的sdk哈

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions.

seeflood commented 2 years ago

done. #568

seeflood commented 2 years ago

image

seeflood commented 2 years ago
seeflood commented 2 years ago
seeflood commented 2 years ago
seeflood commented 2 years ago