Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Verwaltet von:

Serverstatistik:

1,5 Tsd.
aktive Profile

mastodontech.de: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.4.3

#rabbitmq

0 Beiträge0 Beteiligte0 Beiträge heute
Cees-Jan Kiewiet :rp: :wm:<p>Seeing the difference in numbers, 10 years apart, countless upgrades and changes to <span class="h-card" translate="no"><a href="https://phpc.social/@reactphp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>reactphp</span></a></span>, merged Sync and Async clients into one non-blocking (fiber) client, many improvements to PHP since, it hypes me up with excitement for what is next. Also added ext-amqp to the comparison: <a href="https://github.com/jakubkulhan/bunny?tab=readme-ov-file#comparison" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/jakubkulhan/bunny?t</span><span class="invisible">ab=readme-ov-file#comparison</span></a> </p><p><a href="https://toot-toot.wyrihaxim.us/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/ReactPHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReactPHP</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/AMQP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMQP</span></a></p>
Cees-Jan Kiewiet :rp: :wm:<p>Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!</p><p><a href="https://toot-toot.wyrihaxim.us/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>php</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/amqp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amqp</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/bunny" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bunny</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/reactphp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reactphp</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a></p>
Emily<p>Moved away from EMQX for my home lab as they moved to a new licensing scheme and dropped features on the community version to <a href="https://hackaday.social/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> 4.1.1. </p><p>After a day of working on it, got <a href="https://hackaday.social/tags/oauth2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oauth2</span></a> into the cluster working, and <a href="https://hackaday.social/tags/ldap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ldap</span></a> backed <a href="https://hackaday.social/tags/mqtt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mqtt</span></a> client logins. </p><p>Not as flashy as EMQX, but fitting my needs so far very well.</p><p>Really wanted unified account management and doing it all through <a href="https://hackaday.social/tags/Authentik" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Authentik</span></a> through oauth2 and it's LDAP outpost is very cool. No more local mqtt accounts 😊 </p><p><a href="https://hackaday.social/tags/Homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Homelab</span></a> <a href="https://hackaday.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a></p>
alexanderadam<p>Oh wow, according to <span class="h-card" translate="no"><a href="https://bird.makeup/users/codetrendr" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>codetrendr</span></a></span> (account should start mirroring soon) <a href="https://ruby.social/tags/LavinMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LavinMQ</span></a> was 🚀 trending on <a href="https://ruby.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHub</span></a> two weeks ago? 🤩</p><p>For those who don't know: it's a <a href="https://ruby.social/tags/MessageQueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MessageQueue</span></a> written in :crystal: <a href="https://ruby.social/tags/CrystalLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrystalLang</span></a> supporting <a href="https://ruby.social/tags/AMQP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMQP</span></a> 0-9-1 (like 🐰 <a href="https://ruby.social/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a>) and <a href="https://ruby.social/tags/MQTT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MQTT</span></a> (popular in 🤖 <a href="https://ruby.social/tags/IoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IoT</span></a>).</p><p>And it was born at <span class="h-card" translate="no"><a href="https://bird.makeup/users/84codes" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>84codes</span></a></span> / <a href="https://ruby.social/tags/84codes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>84codes</span></a>. 🙏🏻</p><p><a href="https://lavinmq.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">lavinmq.com/</span><span class="invisible"></span></a></p><p><a href="https://ruby.social/tags/crystallanguage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crystallanguage</span></a> <a href="https://ruby.social/tags/crystal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crystal</span></a></p>
galvao|galvaoetibr@bsky.social<p>TIL the documentation for <a href="https://phpc.social/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a>'s <a href="https://phpc.social/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>php</span></a> official client needs A LOT of improvement.</p>
Andrija Petrovic<p>Our <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> work on integration with <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> is getting sufficiently stable, so we've got the backbone of our future information system.<br>Now's the time for <a href="https://lor.sh/tags/kafka" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kafka</span></a>, the nervous system.</p>
Cees-Jan Kiewiet :rp: :wm:<p>Needs some tweaks, not capping out the CPU yet on this image conversion 😅 </p><p><a href="https://toot-toot.wyrihaxim.us/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> <a href="https://toot-toot.wyrihaxim.us/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a></p>
Oskar Dudycz 🇺🇦✊<p>"Event Streaming is not Event Sourcing!" is probably the article I'm linking the most from those that I wrote. It's part of my Don Quixote crusade to untangle those terms, as I've seen many significant architectural decisions made without realising those differences. And the consequences were severe.</p><p>There's a skewed perspective conflating <a href="https://hachyderm.io/tags/EventSourcing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EventSourcing</span></a> with <a href="https://hachyderm.io/tags/EventStreaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EventStreaming</span></a>.</p><p>I know those terms sound similar. I know many people tell you that you can use Kafka as an event store, but...</p><p>Event Sourcing is about making decisions, capturing their outcomes (so events) and using them to make further decisions (so events are the state). </p><p>Event Streaming is about moving information from one place to another and integrating multiple components. </p><p>Event stores are databases. They may have similar capabilities as Event Streaming solutions, but the focus is different: <br>- event stores on consistency, durability and quality of data, <br>- event streaming solutions (like <a href="https://hachyderm.io/tags/Kafka" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kafka</span></a>) are focused on delivery, throughput and integration.</p><p>So, to give a bold comparison, saying that Kafka is an event store is almost like saying that <a href="https://hachyderm.io/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> is a database.</p><p>I really like Kafka; I've been using it successfully, along with the Event Sourcing tool. That's why I believe it's important to know the difference and how to compose those tooling instead of mixing them and getting a hangover.</p><p>Check more in my article 👇</p><p><a href="https://event-driven.io/en/event_streaming_is_not_event_sourcing/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">event-driven.io/en/event_strea</span><span class="invisible">ming_is_not_event_sourcing/</span></a></p>
Elizabeth K. Joseph<p>The <a href="https://floss.social/tags/s390x" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>s390x</span></a> open source software team at IBM confirms the latest versions of various software packages run well on <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> on <a href="https://floss.social/tags/IBMZ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IBMZ</span></a> &amp; <a href="https://floss.social/tags/LinuxONE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxONE</span></a></p><p>In November 2024 validation was maintained for over 35 projects, including <a href="https://floss.social/tags/MySQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MySQL</span></a>, <a href="https://floss.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a>, &amp; <a href="https://floss.social/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> </p><p>We also saw community CI added for SuperNOVAs, and CI with binaries for PolyNode &amp; PocketBase</p><p>Full report + how to apply for your own s390x VM for your project: <a href="https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/elizabeth-k-joseph1/2024/12/23/linuxone-open-source-report-november-2024" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">community.ibm.com/community/us</span><span class="invisible">er/ibmz-and-linuxone/blogs/elizabeth-k-joseph1/2024/12/23/linuxone-open-source-report-november-2024</span></a></p>
Xavki<p>How to install your first Rabbitmq broker ?</p><p><a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.social/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> </p><p><a href="https://youtu.be/HpqvwLH7pm0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/HpqvwLH7pm0</span><span class="invisible"></span></a></p>
Xavki<p>What is core concepts in Rabbitmq ?</p><p><a href="https://youtu.be/ex--_0MJQQk" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/ex--_0MJQQk</span><span class="invisible"></span></a></p><p><a href="https://mastodon.social/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a></p>
Andrija Petrovic<p>It will soon turn out that I don't need <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> in order for my cloud to work. But I wouldn't get to this fact without using it for a while. And our first steps in <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> were with <a href="https://lor.sh/tags/lapin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lapin</span></a> ❤️ . It's good to know that we've got <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> support if we come to need it. Unitl then, more refactor needed on our rabbit-helper lib. Now rmi-helper lib needs to emerge and pick up all rmi-related stuff from rabbit-helper (rmi = Remote Method Invocation).</p>
Xavki<p>What ist Rabbitmq ? Introduction</p><p><a href="https://www.youtube.com/watch?v=qYsQYVf_XgU" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=qYsQYVf_Xg</span><span class="invisible">U</span></a></p><p><a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a> <a href="https://mastodon.social/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
Andrija Petrovic<p>Less than 2 weeks later, I've moved quite a bit. My <a href="https://lor.sh/tags/devcontainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devcontainers</span></a> have <a href="https://lor.sh/tags/vscode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vscode</span></a> workspaces on 3 out of 5 containers in the <a href="https://lor.sh/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://lor.sh/tags/compose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compose</span></a> project:<br>1. <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> container for the whole test suite for the <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> helper lib<br>2. <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> container for the identity processor<br>3. <a href="https://lor.sh/tags/node" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>node</span></a> container for the <a href="https://lor.sh/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>svelte</span></a> app<br>4. <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> container - with management, naturally<br>5. <a href="https://lor.sh/tags/postgres" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>postgres</span></a> container</p><p>And now comes the distributed development.</p>
Vedran Mandić<p>My talk went great! :-) </p><p>I had a full "room"!</p><p>And here is my promised repo on dealing with integration tests in <a href="https://hachyderm.io/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotnet</span></a> </p><p>You can see <a href="https://hachyderm.io/tags/testcontainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testcontainers</span></a> utilized, <a href="https://hachyderm.io/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a>, <a href="https://hachyderm.io/tags/xunit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xunit</span></a> custom parallel framework, <a href="https://hachyderm.io/tags/NSubstitute" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NSubstitute</span></a>, <a href="https://hachyderm.io/tags/TestServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TestServer</span></a> and all in <a href="https://hachyderm.io/tags/csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>csharp</span></a> testing e2e <a href="https://hachyderm.io/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://hachyderm.io/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APIs</span></a> with <a href="https://hachyderm.io/tags/auth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>auth</span></a>, <a href="https://hachyderm.io/tags/MySQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MySQL</span></a>, <a href="https://hachyderm.io/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Redis</span></a>, <a href="https://hachyderm.io/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RabbitMQ</span></a> and <a href="https://hachyderm.io/tags/MongoDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MongoDB</span></a>.</p><p><a href="https://github.com/vmandic/dotnet-integration-tested" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/vmandic/dotnet-inte</span><span class="invisible">gration-tested</span></a></p>
Andrija Petrovic<p>The initial <a href="https://lor.sh/tags/devcontainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devcontainers</span></a> setup I had to see running smoothly was just for test.<br>However, the test was not trivial.<br>I built (actually, my son did 😉 😆 ) a fine little lib based on <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> <a href="https://lor.sh/tags/lapin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lapin</span></a> that allows for publishing/consuming Remote Method Invocation (RMI) structs (<a href="https://lor.sh/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>json</span></a>-ized)<br>The <a href="https://lor.sh/tags/devcontainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devcontainers</span></a> setup has 3 nodes: producer, processor and consumer. <br>- Producer publishes a RMI request via <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a><br>- Processor processes the request and publishes the RMI result on the result channel<br>- Consumer consumes the RMI result</p><p>And this works.<br>Now is the time for a more serious setup: <a href="https://lor.sh/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>svelte</span></a> frontend (my younger son built it 😎 ) that will publish identity-related RMIs (register, login, etc) to <a href="https://lor.sh/tags/rabbitmq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rabbitmq</span></a> and a <a href="https://lor.sh/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> based Identity processor that will allow for the basic functionality of the <a href="https://lor.sh/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>svelte</span></a> frontend</p>
Andrija Petrovic

Mastodon got me engaged in #rustlang programming. A year ago I was doing all my stuff in JS5, using almost all of that stuff + #dotnet as a programming contractor.
2024 was a year of change for me as I see piles of my JS5 code becoming technical debt now.
Currently I'm focusing on #rustlang to process messages transferred across a #docker-based cloud by #rabbitmq, with a #svelte-based frontend. Currently it's quite a bunch of new concepts for me to digest, but things are accelerating during the last month or so.

AngesagtLive-Feeds
Über