User:Dustinturp/sandbox
Submission declined on 10 March 2025 by Timtrent (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
Comment: None of your exiting references are fun Reliable Sources and are thus useless to you 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 13:26, 10 March 2025 (UTC)
| File:LavinMQLogo.svg | |
| Original author(s) | CloudAMQP |
|---|---|
| Developer(s) | CloudAMQP |
| Initial release | March 2023[1] |
| Stable release | 2.1.0
/ January 16, 2025 |
| Repository | github |
| Written in | Crystal |
| Operating system | Cross-platform |
| Type | Message broker |
| License | Apache License 2.0 |
| Website | lavinmq |
LavinMQ is a message-broker developed to use the AMQP 0.9.1 protocol. The broker also supports the MQTT 3.1 protocol. Written in Crystal, LavinMQ was developed as a lightweight and high throughput broker. The project is released under the Apache License 2.0.
History
[edit]The project was originated by 84codes lead by CEO Carl Hörberg, and version 1.0.0 released in March of 2023.[2] The first beta released in May of 2022.[3] The name Lavin, originates from the Swedish word for Avalanche. The broker’s creation is inspired by 10+ years of cloud hosting message brokers across multiple cloud platforms.
Architecture
[edit]LavinMQ focuses on the AMQP 0.9.1 protocol. It is Built on the LLVM compiler and compiles down to a single binary. Clients that implement the 0.9.1 protocol can be used with LavinMQ.
All messages are written to disk. Queues are backed by a message store containing segment files that are 8MB by default. The mmap syscall is used for the message segments. To prevent unnecessary memory usage, the segment files are unmapped when not in use. When a file needs to be written or read, it is re-mapped using only the memory needed for the specific segment. Message are appended to the last segment with a timestamp, exchange, routing key, and message headers.
LavinMQ can run on a single node or multiple nodes greater than or equal to 3. A leader node is always present while changes are streamed to the other nodes in real time. When the leader is unavailable an election takes place. Clustering utilizes ETCD, using the Raft consensus algorithm for leader election and maintaining the In-Sync-Replica (ISR) set.
See also
[edit]
References
[edit]- ^ CLoudAMQP. "LavinMQ Release". Retrieved 15 January 2025.
{{cite web}}: CS1 maint: url-status (link) - ^ Christina Dahlén (April 4, 2023). "v1.0.0 Release". Press release. Retrieved March 5, 2025.
- ^ "v1.0.0-beta.1 Release". Press release. May 19, 2022. Retrieved March 5, 2025.
- in-depth (not just passing mentions about the subject)
- reliable
- secondary
- independent of the subject
Make sure you add references that meet these criteria before resubmitting. Learn about mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.