HEherogary·Mar 8, 2023Submission
Programming framework for writing and deploying cloud applications
3 points · Open discussionServiceWeaver
weaver
Go2023–2023
ServiceWeaver / weaver · Archived
weaver
Programming framework for writing and deploying cloud applications.
2Distinct people
2Mentions
0Explicit recommenders
4.8KGitHub stars
What to know before exploring
What it is
Programming framework for writing and deploying cloud applications.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 3-hour interval2 dated mentions
Observed mentions: 2023-03-05 00:00:00 UTC to 2023-03-08 02:14:09 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 5, 00:00 | 2023-03-05 00:00:00 UTC | 2023-03-05 03:00:00 UTC | 1 | 0 | 1 |
| Mar 5, 03:00 | 2023-03-05 03:00:00 UTC | 2023-03-05 06:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 06:00 | 2023-03-05 06:00:00 UTC | 2023-03-05 09:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 09:00 | 2023-03-05 09:00:00 UTC | 2023-03-05 12:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 12:00 | 2023-03-05 12:00:00 UTC | 2023-03-05 15:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 15:00 | 2023-03-05 15:00:00 UTC | 2023-03-05 18:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 18:00 | 2023-03-05 18:00:00 UTC | 2023-03-05 21:00:00 UTC | 0 | 0 | 0 |
| Mar 5, 21:00 | 2023-03-05 21:00:00 UTC | 2023-03-06 00:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 00:00 | 2023-03-06 00:00:00 UTC | 2023-03-06 03:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 03:00 | 2023-03-06 03:00:00 UTC | 2023-03-06 06:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 06:00 | 2023-03-06 06:00:00 UTC | 2023-03-06 09:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 09:00 | 2023-03-06 09:00:00 UTC | 2023-03-06 12:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 12:00 | 2023-03-06 12:00:00 UTC | 2023-03-06 15:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 15:00 | 2023-03-06 15:00:00 UTC | 2023-03-06 18:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 18:00 | 2023-03-06 18:00:00 UTC | 2023-03-06 21:00:00 UTC | 0 | 0 | 0 |
| Mar 6, 21:00 | 2023-03-06 21:00:00 UTC | 2023-03-07 00:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 00:00 | 2023-03-07 00:00:00 UTC | 2023-03-07 03:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 03:00 | 2023-03-07 03:00:00 UTC | 2023-03-07 06:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 06:00 | 2023-03-07 06:00:00 UTC | 2023-03-07 09:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 09:00 | 2023-03-07 09:00:00 UTC | 2023-03-07 12:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 12:00 | 2023-03-07 12:00:00 UTC | 2023-03-07 15:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 15:00 | 2023-03-07 15:00:00 UTC | 2023-03-07 18:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 18:00 | 2023-03-07 18:00:00 UTC | 2023-03-07 21:00:00 UTC | 0 | 0 | 0 |
| Mar 7, 21:00 | 2023-03-07 21:00:00 UTC | 2023-03-08 00:00:00 UTC | 0 | 0 | 0 |
| Mar 8, 00:00 | 2023-03-08 00:00:00 UTC | 2023-03-08 03:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesOne of the reasons I break code down into smaller pieces ( microservice ) is to have fast edit and compile times.
The versioning hell is why so many went to mono repos. There is only one git version and that’s it.
Also what about runtime version difference and schema evolution?
So many thing come into play.
I would rather just buy the bullet and use protobufs with NATS from day one . No load balances and heavy expensive gke / k8 stuff
Then deploy of fly where I have regions with auto scaling based on metric feedback loops.
Then use nats client on all client to get geo physical load balancing out to the nearest region.
Then use their postresql multi Region. Cockroach multi Region replication costs big money.
I did like their tooling in Weaver though. Even the converged logging was pretty nice.
https://github.com/ServiceWeaver/weaver/blob/m