Petr

count(1 1 2 3 5 8 13 8 5 3 2 1 1)=13 Planing Tree For Life Prediction

[Petr @globallink_]

Our goal is to strive towards betterment of Universe...

[Path of Men @PathOfMen_]

Just start

[sent @sentdm]

One API. Send messages on all channels.

[GitHub Projects Community @GithubProjects]

Run a full virtual desktop inside a Docker container, accessible via WebRTC, right from your browser.

[Petr @globallink_]

@kurosci Hello world

[javinpaul @javinpaul]

The Software Design Interview Preparation RoadMap (with Resources) - https://t.co/5PoGb6ceqC

[Petr @globallink_]

Тупой бред, с одеть и надеть. То есть себя я не могу одеть, а могу одеть что либо на другого, либо на что то. Но получается фразы «иди оденься» и «иди переоденься» неверны. Человек может только надеться, но слово сразу режет слух. Так же, кто либо, не может переодеться.

[Орчибальд и Айфоны @orchibald1]

iPhone 16 pro max 256 gb

133к Карл 😱

Можно оформить в рассрочку/кредит до 24 месяцев ✅

Самое время закупиться ☺️

Еще у нас появились
PlayStation 5 Pro⚡️

https://t.co/lThI4EtB3I

[Petr @globallink_]

@Polard2007 @Hokagess Поэтому предприятия дорожат репутацией и делают все возможное, но не в этом случае

[Rishabh @Rixhabh__]

12 websites to earn $100/hour:

[Petr @globallink_]

@callsgiorgio69 Это не про меня было)

[Buitengebieden @buitengebieden]

No way.. 🤯 https://t.co/gG0jwCEQyN

[Inferam @InferamAI]

https://t.co/66MH8cCNE6

[Massimo @Rainmaker1973]

When mushrooms kick in

[Bytebytego @bytebytego]

IBM MQ -> RabbitMQ -> Kafka ->Pulsar, How do message queue architectures evolve?

🔹 IBM MQ
IBM MQ was launched in 1993. It was originally called MQSeries and was renamed WebSphere MQ in 2002. It was renamed to IBM MQ in 2014. IBM MQ is a very successful product widely used in the financial sector. Its revenue still reached 1 billion dollars in 2020.

🔹 RabbitMQ
RabbitMQ architecture differs from IBM MQ and is more similar to Kafka concepts. The producer publishes a message to an exchange with a specified exchange type. It can be direct, topic, or fanout. The exchange then routes the message into the queues based on different message attributes and the exchange type. The consumers pick up the message accordingly.

🔹 Kafka
In early 2011, LinkedIn open sourced Kafka, which is a distributed event streaming platform. It was named after Franz Kafka. As the name suggested, Kafka is optimized for writing. It offers a high-throughput, low-latency platform for handling real-time data feeds. It provides a unified event log to enable event streaming and is widely used in internet companies.

Kafka defines producer, broker, topic, partition, and consumer. Its simplicity and fault tolerance allow it to replace previous products like AMQP-based message queues.

🔹 Pulsar
Pulsar, developed originally by Yahoo, is an all-in-one messaging and streaming platform. Compared with Kafka, Pulsar incorporates many useful features from other products and supports a wide range of capabilities. Also, Pulsar architecture is more cloud-native, providing better support for cluster scaling and partition migration, etc.

There are two layers in Pulsar architecture: the serving layer and the persistent layer. Pulsar natively supports tiered storage, where we can leverage cheaper object storage like AWS S3 to persist messages for a longer term.

Over to you: which message queues have you used?

–
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/FIzCeaWsZV

[Security Trybe @SecurityTrybe]

Linux Cheatsheet