TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

RabbitMQ 3.11 Feature Preview: Super Streams

95 点作者 codeadict将近 3 年前

5 条评论

kungfufrog将近 3 年前
If I had to nominate a piece of software, as an SRE, that is as close to &quot;set and forget&quot; as possible, it&#x27;d absolutely be RabbitMQ standalone and a close runner up would be its clustered form.<p>I&#x27;ve worked in 3 places where RabbitMQ has been a fundamental cornerstone of the architecture, and while it does require a little tuning around performance occasionally (generally because it&#x27;s being used inappropriately or without full consideration of its limitations&#x2F;best practices), it&#x27;s rock solid, easy to debug&#x2F;inspect, has an active and supportive community, and is generally just all around pleasant to work with and maintain.<p>Kudos to RabbitMQ and its developers!<p>As an aside, the addition of recent features such as super streams, streams and quorum queues make it a compelling all-in-one tool for solving a bunch of architectural based concerns&#x2F;requirements in application and infrastructure development. I&#x27;ve often thought about why it&#x27;s not more utilised in the ops side of the world for metrics gathering and other usecases. I have also wondered how useful it&#x27;d be for log ingestion with lazy queues etc.<p>Does anyone out there have examples of unusual use cases for RabbitMQ where it&#x27;s outshone some alternative product? Would love to hear about them!
评论 #32089762 未加载
评论 #32090289 未加载
评论 #32089669 未加载
评论 #32091628 未加载
评论 #32090483 未加载
评论 #32092905 未加载
hnrodey将近 3 年前
My own blog post:<p>What I Wish Someone Would Have Told Me About Using Rabbitmq Before It Was Too Late<p><a href="https:&#x2F;&#x2F;ryanrodemoyer.github.io&#x2F;what-i-wish-someone-would-have-told-me-about-using-rabbitmq-before-it-was-too-late&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ryanrodemoyer.github.io&#x2F;what-i-wish-someone-would-ha...</a>
评论 #32090742 未加载
FridgeSeal将近 3 年前
A bit of a weird article. It announces super streams-which are basically topic partitions in Kafka, acknowledges that, but then hand-waves “oh but they’re different” and then spends the rest of the article talking about all the features that are identical to how topic partitions work…<p>It’s a good feature, there’s nothing wrong with that, but there’s nothing wrong with saying “we’ve brought this feature to RabbitMQ too” rather than trying to pretend it’s totally-not-the-same.
评论 #32090581 未加载
latch将近 3 年前
I read the blog post and the Java documentation (which is more informative), and maybe I missed it, but I can&#x27;t figure out how you define the # of streams&#x2F;partitions. Is it defined when the superstream is created?<p>What&#x27;s the general practice for multi-tenancy? Say we have millions of clients with thousand being added daily and for various reasons, at least for _some_ message types, we&#x27;d like to keep them separate (for example, maybe strict ordering is super important, so we can&#x27;t throw messages away, but we don&#x27;t want a poison message to impact all customers).
评论 #32094783 未加载
scumola将近 3 年前
TIL: RabbitMQ is written in erlang