The better stack rn is buf + Connect RPC: https://connectrpc.com/ All the compatibility, you get JSON+HTTP & gRPC, one platform.
HN user
perezd
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!
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!
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 :)
Correct. WarpStream doesn't even support transactions.
It isn't.
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!
You probably want to check this out: https://connectrpc.com/
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
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
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.
If you are wondering wtf editions are, I wrote a blog post about it here: https://buf.build/blog/protobuf-editions-are-here
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.
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 :)
If we look back at some point, and Google falls apart/becomes irrelevant, that'll be on Sundar.
Google is days away from making Protobuf Editions GA. Never heard of it? Read on.
Its not that complex. CouchDB is the core technology that Couchbase and BigCouch, et. al are using to power their more "vertical" offerings, in various degrees. CouchDB is not going anywhere, and its a great standalone product.
This is where actual innovation is happening. I'm not at all discouraged by the FUD being perpetuated by Katz today. I have a fairly modest BigCouch deployment in production and I am very happy with it. haters gonna hate.
Now CouchDB's _changes can support websockets!
I want to be as cool as this guy when I grow up.
I really want to believe the mouthpiece over at Microsoft, he makes a convincing argument, "nobody is skilled in HTML _5_", what does that even mean? Clearly this guy doesn't even know what he is battling here.
Everyone knows business apps don't need to be cross platform, and none of us know what we're doing. I won't even waste my time listing the tools available for modern JS projects, especially for data-centric applications.
What we need are MORE single-platform alternatives! Because anyone who is actually getting work done, is doing it on the platform made by the company who is writing my checks!
What a tool.
On the surface Orchestra looks like any number of to-do lists, but beneath it's actually a real-time messaging system. Think group chat for getting things done, with sync that just works without ever having to "pull-to-refresh" (so 2009). Also, welcome to Hacker News!
We want to build that tool, maybe you should work with us? :) I hope you come to love our product, what you are describing is what we are trying to build as a company. Give us feedback, please!
We hear you. We're focused on bringing Orchestra to more platforms, we're hiring, too! If anyone is interested in working on this with us, we're hiring jobs (at) orchestra (dot) com, mention HN.
link is dead :(, can this be seen anywhere else?
This is fantastic! Thank you for contributing this back to the community.
This is not true. read the release notes.
This is a huge release. Replicator was effectively re-written, much faster internals, HTTPS support is native. These features are warmly welcomed! Excited to see this now integrated into BigCouch!
Share your tips too, here in the comments, or on the article itself.
I've used it in the past for a logging tool that we wrote for our production app servers. I was super unimpressed with it. Bindings (for ruby) at the time really sucked, and were not clear which ones to use.
Also, SLOW. HTTP WAN db access is what you expect it to be.
Lastly, I don't like their data storage format at all, arrays of arrays, is painful and requires a lot of hoop jumping at times.
We switched to a local mongodb server as a near drop-in replacement, and it was a billion time faster and more efficient.
The final nail in the coffin was the data storage per record limitation, I think it was 1MB or something, so it was easy to piss off when capturing stack traces, hardly better than syslog at that point.
Ultimate CSS Gradient Generator? Try using Compass (www.compass-style.org) They have mixins and color calculation functions builtin that make this a trivial 1 line of code thing to do, in Sass. It even generates supported directives for all browsers that currently have support for gradients.