thanks.
Wondering if there any examples of this ?
15 karma · joined April 26, 2021
thanks.
Wondering if there any examples of this ?
It avoids all the GPRC mess You can instead use Proto and let NATS be be Transport.
Is there any suppptt for Publishing an event to all subscribes from a Module so all other modules that are interested could get that event payload ?
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/main/runtime/lo...
https://github.com/orgs/ergo-services/repositories Is erlang written in golang.
The examples are great and clearly shows what it offers in terms of failure scenarios that it handles. Supervisors tress etc.
Weaver with ergo would be a nice mix ?
You don’t specify your physical topology in code but instead at deployment time. Weaver gke but written for ergo where the Trees are decided at deployment time perhaps.
This golang package helps to remedy that by providing a bus / messsge queue that can run in process or over the network.
So you get rpc without thinking about it and failure is managed by the data plane forwarding the message when the network is healthy again.
https://github.com/suborbital/e2core/blob/main/foundation/bu...
This however forces all other code using a package like this to adapt to the realities that you’re in an async non blocking world now. A rpc call will give you a response eventually.
So the calling func and all parent funcs will just have to wait around when the network is unhealthy?
Can we render on server , then upgrade to render on client progressively?
Also can we load other wasm using server push in the background . You get runtime plugins then
I have been using quic with golang and am looking forward to trying this out
I use hetzner already too.
Do you happen to have an makefiles or scripts that set up this on your mac that you can share ?
has GUi tooling also.
https://github.com/dosco/graphjin
You give it the Postresql script and you will see the new GraphQL schema in he GUI, ready to test. This means that is only one change point ever - the sql.
It also supports subscriptions.
for CI you can just put the script into your git tree and it will pick them up at the start of a deploy update.