![]() ![]() With messaging systems, apart from simple functionality such as adding and popping items from the queue, you get additional benefits such as delivery guarantee, durability, routing and more. A messaging system could act as such an interface. But if we already have more sophisticated architecture, consisting of more than one service and we need to guarantee that the queue doesn’t disappear on server restart, then delivering new items in the queue requires an advanced interface. In case of a simple in-memory queue, adding and popping items from the queue is not a big deal. Stories on software engineering straight to your inbox Sign up for newsletter How skillfully developer is able to use collections, and especially queues, to solve problems, defines his level of competence. Queueing theory, which could be very useful when we need to design complex systems. In programming, such type of collection is called aĭanish engineer and mathematician even created a We can see examples of such processes everywhere in real life. ![]() Actually, it doesn’t matter how much data we need to process, we just pick one element from the collection and process it, then pick the next one. ![]() We can do it sequentially or use multiple threads and then things will go faster. In such a situation, we can stop receiving new data until we finish processing the current one, or we just add each next piece of data to the collection and continue processing it one by one. In programming, especially in the era of microservices, we encounter situations when we need to process more data than we can handle in one moment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |