[Serverless] Case: monolithic deployment
维护者通常 7 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- csharp
调研方向
Start with the linked Wait strategy in the read-model concept docs and compare it with the three approaches described here. The issue does not name code files or tests; first identify the subscription and command API entry points that implement read-model waiting. Done means choosing and implementing a serverless approach that reliably waits for all produced events to be processed, with behavior and tests defined.
由索引模型根据 Issue 内容生成。
描述
How to make subscriptions work in a serverless world?
Simplest scenario: monolithic deployment
The whole application represents a single bounded context, where commands and queries are combined into a single deployment unit. Such an application would include all the necessary components:
- Command services
- Command APIs
- Query services
- Read model subscriptions
- Gateways
There are two ways to make it work:
- Just do nothing. Expect the function/container timeout to be enough for all the subscriptions to handle newly produced events. It would work in many cases, but there's no resilience against external infrastructure failures for event handler targets.
- Ensure the command is handled in an asynchronous unit of work. The command service would do its thing, as usual; there's no change required. Subscriptions would expose an internal HTTP API to report the last processed event position. A new function is needed to poll the API from inside the service, simulating traffic until all the subscriptions get beyond the position of the last produced event. It will prevent the function from being shut down (in theory).
- Ensure the command is handled in a synchronous unit of work. The command API will block until all subscriptions handle all the produced events in the application. It requires some method of internal asynchronous communication. Subscriptions will produce internal messages with the latest processed event position. The command API can observe these messages, so it can ensure that all the new events are handled. After that's confirmed, the command API returns the response as usual.
The last point also applies to non-serverless scenarios, where we must ensure that read models are updated. It essentially implements the Wait strategy from the docs.
- 主要语言
- C#
- 星标
- 512
- 派生
- 99
- 平均合并
- 5 天 6 小时
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Eventuous/eventuous 的其他 Issue
-
MongoDB integration tests fail on newer GitHub Actions runner kernels可能已有人在做 @nmummau 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
Eventuous/eventuous#626 · 2 条评论 ·
维护者通常 7 天内回复
-
`dotnet format style --verify-no-changes` fails with naming violations and unnecessary imports可能已有人在做 @nmummau 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
Eventuous/eventuous#624 · 1 条评论 ·
维护者通常 7 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
Eventuous/eventuous#627 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: `append_events` does not need the `@inserted` table variable可能已有人在做 @nmummau 于 7 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 20/100
Eventuous/eventuous#619 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: stream reads do one key lookup per event, and `IDX_EventsStream` duplicates `UQ_StreamIdAndStreamPosition`可能已有人在做 @nmummau 于 7 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 18/100
Eventuous/eventuous#618 · 1 条评论 ·
维护者通常 7 天内回复
查看 Eventuous/eventuous 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
joinrpg/joinrpg-net#5752 ·
维护者通常 1 天内回复
-
bug ux
难度 2/5 1-3 小时 新手友好度 78/100
CodeForFire/lagebuch#714 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
dimitar-radenkov/Pointframe#294 ·
维护者通常 1 天内回复
-
kind/feature-request
难度 2/5 1-3 小时 新手友好度 68/100
Altinn/altinn-correspondence#2154 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 61/100
Okabintaro/SubmersedVR#253 ·