モジュラモノリスについて気になること

モジュールごとにアイデンティティを分けられるか

テーブルのアクセス制御

あらゆるコンポーネントのアクセス制御

メモリ空間が同一なら難しそうだが、ガードレール程度の隔離ならできそう

ロックステップリリースできるのか

Service Weaver

Service Weaver takes a different approach to rollouts and sidesteps these complex cross-version interactions. Service Weaver ensures that client requests are executed entirely within a single version of a system. A component in one version will never communicate with a component in a different version. This eliminates the leading cause of update failures, allowing you to roll out new versions of your Service Weaver application safely and with less headache.

フレームワークが死んだ場合の出口戦略、またはフレームワークレスの実装

実際 Service Weaver が死んでそう…

Service Weaver began as an exploratory initiative to understand the challenges of developing, deploying, and maintaining distributed applications. We were excited by the strong interest from the developer community, which led us to open-source the project.

We greatly appreciate the continued advocacy and support of the Service Weaver community. However, we realized that it was hard for users to adopt Service Weaver directly since it required rewriting large parts of existing applications. Therefore, Service Weaver did not see much direct use, and effective December 5, 2024, we will transition Service Weaver into maintenance mode. After this date, for the next 6 months, we will only push critical commits to the GitHub repository, respond to critical issues, merge critical pull requests, and patch new releases. We recommend that users fork the repository and report any issues preventing them from maintaining a stable version of the code.

On June 6, 2025, we plan to permanently freeze and archive the GitHub repository, after which no new commits or releases will be made.