perezd
Joined 19 years ago
Karma
411
Submissions
95
Member since
Aug 28
Recent submissions
Comment · 1 year ago
The better stack rn is buf + Connect RPC: https://connectrpc.com/
All the compatibility, you get JSON+HTTP & gRPC, one platform.
Comment · 2 years ago
That's correct. Bufstream is not open source, but we do have a demo that you can try. I've asked the team to include a proper LICENSE file as well. Thanks for catching that!
Comment · 2 years ago
That's correct. We hop onto Zoom calls with our customers on an agreed cadence, and they share a billing report with us to confirm usage/metering. For enterprise customers specifically, it works great. They don't want to violate contracts, and it also gives us a natural check-in point to ensure things are going smoothly with their deployment.
When we say fully air-gapped, we mean it!
Comment · 2 years ago
Nope! We're still heavily investing in scaling Protobuf. In fact, our data quality guarantees built into Bufstream are powered by Protobuf! This is simply an extension of what we do...Connect RPC, Buf CLI, etc.
Don't read too much into the website :)
Comment · 2 years ago
Correct. WarpStream doesn't even support transactions.
Comment · 2 years ago
It isn't.
Comment · 2 years ago
It'd be cool if you supported the Buf Schema Registry's Reflection API: https://buf.build/docs/bsr/reflection/overview
Then, the descriptors could be delivered on demand!
Comment · 2 years ago
You probably want to check this out: https://connectrpc.com/
Comment · 2 years ago
I think that's not true. There are plenty of incremental ways to adopt gRPC. For example, there are packages that can facade/match your existing REST APIs[1][2].
Reads like a skill issue to me.
[1]: https://github.com/grpc-ecosystem/grpc-gateway [2]: https://github.com/connectrpc/vanguard-go
Comment · 2 years ago
Protobuf can typically be about 70-80% smaller than the equivalent JSON payloads. If you care about Network I/O costs (at a large scale), you'd probably want to realize a benefit in cost savings like that.
Additionally, I think people put a lot of trust into JSON parsers across ecosystems "just working", and I think that's something more people should look into (it's worse than you think): https://seriot.ch/projects/parsing_json.html
Comment · 2 years ago
I think it's helpful for engineering managers to be technically conversant at a fairly deep level with the technical challenges and domains the team deals with regularly. My reports have told me that in the past, this bolstered their trust in my decision-making and gave me deeper credibility overall.
I didn't do anything terribly difficult/deep, but I think it conveyed a strong, empathetic connection to what they were dealing with that mattered to them.
Comment · 2 years ago
If you are wondering wtf editions are, I wrote a blog post about it here: https://buf.build/blog/protobuf-editions-are-here
Comment · 2 years ago
lol, well. Sorry man, I'm a real boy. Check my account age. I can solve some math problems or look at what photos are bridges if you want.
Comment · 2 years ago
Many folks don't know about what Protobuf Editions are, and it's about to be generally available. I was encouraging people to read the article :)