One 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 mo

One 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/main/runtime/logging/files.go https://github.com/ServiceWeaver/weaver/blob/main/runtime/lo...