多租户,其实是在用户这层之上,抽象出了一层account。
账户和账户之间,资源都是隔离的,同时,账户和账户之间也可以通过export或者import来共享一些这个主题的消息。
使用场景:在一个企业内,只部署了一套nats服务,但是有很多个应用都需要使用这套nats服务,但是应用和应用之间的这个消息相互之间是完全隔离的,那这就能用到这种多租户的架构。
多租户配置详解:
- Streams are messages your application publishes. Importing applications won’t be able to make requests from your applications but will be able to consume messages you generate.
- Services are messages your application can consume and act on, enabling other accounts to make requests that are fulfilled by your account.
accounts: {
A: {
users: [
{user: a, password: a}
]
exports: [
{stream: puba.>}
{service: pubq.>}
{stream: b.>, accounts: [B]}
{service: q.b, accounts: [B]}
]
},
B: {
users: [
{nkey: UXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX}
]
imports: [
{stream: {account: A, subject: b.>}}
{service: {account: A, subject: q.b}}
]
},
C: {
users: [
{user: c, password: c}
]
imports: [
{stream: {account: A, subject: puba.>}, prefix: from_a}
{service: {account: A, subject: pubq.C}, to: Q}
]
},
}
no_auth_user: a
本文发表于 0001-01-01,最后修改于 0001-01-01。
本站永久域名「 jiavvc.top 」,也可搜索「 后浪笔记一零二四 」找到我。