Is it still in active development?

[siftbits]

Thanks for this meaningful project.
Our team resonates with the theories it presents, and we are planning to develop our new product based on this framework.
However, after some research, we noticed that the recent activity in issue tracking, PRs, Google Groups, and Discord seems quite low.
Could you please let us know if this project is still actively being developed? What is the roadmap moving forward?
Thank you.

BTW, I’ve seen others raise similar questions on Discord as well.

For who care about : Important Announcement

[rezkam]

+1

[bagualing]

However, after some research, we noticed that the recent activity in issue tracking, PRs, Google Groups, and Discord seems quite low.

+1
The development work of Service Weaver seems to be temporarily suspended. Is it due to technical bottlenecks, insufficient resources or other reasons?

[ermanimer]

+1
We are also planning to use service weaver for a new project.

[aliuygur]

+1

[xeynyty]

+1

[czyt]

+1

[meifannao]

+1

[bozkurtemre]

+1

[bagualing]

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.

[xinjiayu]

It's a great pity that we have already begun utilizing this framework in production environments. I've always believed this to be a remarkable idea, yet its limited usage can likely be attributed to insufficient promotion. Many are unaware of its existence, which explains the low adoption rate. Nevertheless, this framework truly deserves recognition, and I genuinely hope it can sustain its growth.

[MakiJOJO]

It's a great pity that we have already begun utilizing this framework in production environments. I've always believed this to be a remarkable idea, yet its limited usage can likely be attributed to insufficient promotion. Many are unaware of its existence, which explains the low adoption rate. Nevertheless, this framework truly deserves recognition, and I genuinely hope it can sustain its growth.

@xinjiayu I am also attracted by the concept of this framework, but because the official version has not been released, I dare not use it in the production environment. I want to know if its experience in development, deployment, operation and maintenance is better than the traditional micro service framework in the past?

[chouxuka]

oh my god! Our new project is being developed using service weaver and ready to go live

[haydenflinner]

I don't understand why archive the central gathering place for the project rather than just let it be, awaiting someone to take over maintainership. Plenty of folks in this thread apparently ready to go to production, which means it must work well enough to be left alone. What is being avoided by archiving, besides the easiest path continued growth?

[rootless-dev]

+1