Does it have a similar system to Jetstream? If yes, does it address the reliability issues Jetstream has been criticized about lately?
Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
21–30 of 78 posts
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#22Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#23[flagged]
you need to touch grass
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#24Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#25Earlier quoted context omitted.
Anyone can buy a 9950x on Amazon or any tech store, it's consumer hardware.
Given that this entire project is a single[1] vibe-coded commit, I really doubt the author bothered buying hardware to test it. [1]: https://github.com/bustermq/bustermq/commits/master/
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#26Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#27[flagged]
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#28Upvote for Bazel. I think these days I place a lot more value on how well an ecosystem slots into Bazel/friends because monorepos are increasingly more useful and relevant. So nice to see there are good rules for Zig and that folks are using them. Also ironically I think starting with Bazel/Buck/whatever your poison of choice is almost always a good move even if people tell you it's overkill. The easiest time to do i…
Downvote for this web site is a horror movie billboard and zig already has a build system which is zig and that's one of it's neat features.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#29Earlier quoted context omitted.
The problem with "the language tooling is already a build system" is that cross-language dependency chains are a thing. The moment you need a Rust or Zig file to be regenerated and recompiled when a JSON schema or .proto file is updated, you're outside what most of those language-specific toolchains can support. This is where Bazel absolutely shines.
If all of your dependencies need to use the same build system as your project then your build system/process is defect anyway. It should be possible to invoke a foreign build system as part of your build.
perhaps, just perhaps, why people go through the trouble not because they are idiots but for actual engineering reasons
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#30Earlier quoted context omitted.
The problem with "the language tooling is already a build system" is that cross-language dependency chains are a thing. The moment you need a Rust or Zig file to be regenerated and recompiled when a JSON schema or .proto file is updated, you're outside what most of those language-specific toolchains can support. This is where Bazel absolutely shines.
Zig build system can do all that just fine though