Should I read past page one?

1-bob qolib ketdi

Understanding messaging
This chapter covers
 Messaging concepts—consumers, producers, and brokers
 AMQP elements—exchanges, queues, and bindings
 Virtual hosts
 Message durability
 The life of a message from producer to consumer
Ushbu bob qamrab oladi
 Xabar tushunchalari - iste'molchilar, ishlab chiqaruvchilar va brokerlar
 AMQP elementlari — almashishlar, navbatlar va bog‘lashlar
 Virtual xostlar
 Xabarning chidamliligi
 Ishlab chiqaruvchidan iste'molchiga xabarning hayoti

When you say messaging, programmers think of a lot of different things. Email and IM come most readily to mind, but these models aren’t what we mean when we talk about messaging in terms of RabbitMQ. Messaging in RabbitMQ has some elements in common with email and IM, but is a completely different paradigm. For

example, while AMQP, like email, stores messages for consumers who aren’t online, those messages are routed based on tags that are much more flexible. Also different from email, the messages have no set structure and can even store binary data directly. Unlike IM protocols, AMQP hides the sender and receiver from each other.
There’s no concept of presence. As a result, you have a flexible infrastructure that encourages pervasive decoupling of your applications. AMQP messages can be routed one-to-many both in a broadcast pattern or selectively, as well as one-to-one. With IM you typically only get one-to-one.

Xabarlar deganda, dasturchilar juda ko'p turli xil narsalarni o'ylashadi. E-pochta va tezkor xabarlar esga eng oson keladi, ammo RabbitMQ nuqtai nazaridan xabar almashish haqida gapirganda, bu modellar biz nimani nazarda tutmaydi. RabbitMQ-da xabar almashish elektron pochta va IM bilan umumiy bo'lgan ba'zi elementlarga ega, ammo bu butunlay boshqacha paradigma. Masalan, elektron pochta kabi AMQP onlayn bo'lmagan iste'molchilar uchun xabarlarni saqlasa-da, bu xabarlar ancha moslashuvchan teglar asosida yo'naltiriladi. Bundan tashqari, elektron pochtadan farqli ravishda, xabarlar o'rnatilgan tuzilishga ega emas va hatto ikkilik ma'lumotlarni to'g'ridan-to'g'ri saqlashi mumkin. IM protokollaridan farqli o'laroq, AMQP jo'natuvchi va qabul qiluvchini bir-biridan yashiradi.

Mavjudlik tushunchasi yo'q. Natijada, sizda ilovalaringizning keng tarqalgan ajratilishini rag'batlantiradigan moslashuvchan infratuzilma mavjud. AMQP xabarlari translyatsiya sxemasida ham, tanlab ham, birdan ko‘pga ham, birma-bir yo‘naltirilishi mumkin.
IM bilan siz odatda faqat birma-bir olasiz.

Since AMQP messaging is different from other messaging protocols, we’ll spend the next few sections explaining the lingo and building blocks of AMQP. If you have a good basis in enterprise messaging systems like TIBCO or IBM’s MQSeries, a lot of this will be familiar. Because RabbitMQ’s focus is on application-to-application messaging, it’s important to understand the concepts of that messaging pattern clearly. Let’s start

by forgetting the client/server distinction we’ve had ingrained in us and begin figuring out consumers and producers.

AMQP xabar almashish boshqa xabar almashish protokollaridan farq qilganligi sababli, biz keyingi bir necha bo'limni AMQP tili va qurilish bloklarini tushuntirishga sarflaymiz. Agar siz TIBCO yoki IBM MQSeries kabi korporativ xabar almashish tizimlarida yaxshi asosga ega bo'lsangiz, bularning ko'pi tanish bo'ladi. RabbitMQ-ning asosiy e'tibori ilovadan ilovaga xabar almashishga qaratilganligi sababli, ushbu xabar almashish namunasi tushunchalarini aniq tushunish muhimdir. Keling, bizda o'rnatilgan mijoz/server farqini unutib, iste'molchilar va ishlab chiqaruvchilarni aniqlashni boshlaylik.