rabbitmq

¡Construye una API HTTP desde 0 con Scala! Servidor HTTP, parsing de JSON, integración con base de datos, publicación de eventos en RabbitMQ, tests de aceptación y unitarios, y mucho más! ???? Este curso y muchos más en CodelyTV Pro! ???? http://bit.ly/curso-api-scala

Queues are a great addition to any application that has some tasks that need processing asynchronously. This could be sending a confirmation email, resizing an avatar, or recalculating a running total of some kind; in all those cases it would be cool to send the response back to the user and then sort out that task later. This session looks at how to use a RabbitMQ job queue in your application. It also looks at how to design elegant and robust long-running workers that will consume the jobs from the queue and process them. This session is ideal for technical leads, developers and architects alike.

Pub-Sub / Publish-Subscribe"In software architecture, publish–subscribe is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers, but instead categorize published messages into classes without knowledge of which subscribers, if any, there may be. Similarly, subscribers express interest in one or more classes and only receive messages that are of interest, without kn...

Pub-Sub / Publish-Subscribe"In software architecture, publish–subscribe is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers, but instead categorize published messages into classes without knowledge of which subscribers, if any, there may be. Similarly, subscribers express interest in one or more classes and only receive messages that are of interest, without kn...

TL;DR A queue is a good choice when you have one kind of job to do that you can divide in independent smaller jobs that can execute in any order and a distributed log is a good choice when you have several kinds of jobs or functionalities for the same stream of data (logs, events, etc.).Queues vs Distributed LogsThis blog post tries to explain the typical use for Queues and for Distributed Log, but of course, a system usually uses these solutions in combination or in other ways. But I...

TL;DR A queue is a good choice when you have one kind of job to do that you can divide in independent smaller jobs that can execute in any order and a distributed log is a good choice when you have several kinds of jobs or functionalities for the same stream of data (logs, events, etc.).Queues vs Distributed LogsThis blog post tries to explain the typical use for Queues and for Distributed Log, but of course, a system usually uses these solutions in combination or in other ways. But I...

Puneet is an experienced Groovy & Grails developer in TO THE NEW Digital who loves coding and enjoy finding optimized solutions for the problems. He's passionate about exploring new technologies and using them to solve the business needs. He recently presented in Gr8Conf India. He along with team started contributing to open source by migrating around 20 plugins to Grails 3 including Jodatime, Elasticserach, Asynchronous Mail & RabbitMQ. He has been a part of knowledge sharing team in TO THE NEW Digital. He also motivates and promotes sharing of knowledge across the whole Grails team. Hubert Klein Ikkink is also known as mrhaki. He uses this alias to write on his blog “Messages from mrhaki”. On this blog he writes short tips and tricks about Groovy features in the “Groovy Goodness” series. Hubert started to develop Java applications more than a decade ago. Six years ago he started to explore Groovy and Grails in personal projects, because of the dynamic nature of Groovy and the speed of development. Today he works with Groovy and Grails during his daytime job at JDriven in the Netherlands.

En el video pasado, vimos cómo distribuir eventos de forma usando una REST API. En este video, veremos cómo distribuir eventos usando un sistema de colas como RabbitMQ, qué detalles hay que tener en cuenta y algunos trucos para facilitarnos el trabajo.

En febrero contamos con un ponente de altura, Don Alvaro Videla, que aprovechando que se encuentra en Madrid, se pasará por PHPMad para darnos su charla "Introducción a RabbitMQ" Descripción de la charla: Do you need to process thousands of images in the background for your web app? Do you need to share data across multiple applications, probably written in different languages and sitting at different servers? Your real time data feed is becoming slow because you are polling the database constantly for new data updates? Do you need to scale information processing during peek times? What about deploying new features with zero downtime? If any of these problems sound familiar then you probably need to use messaging in your application. In this talk I will introduce RabbitMQ, a messaging and queue server that can help us tackle those problems. We will learn the benefits of a Queue Server and see how to integrate messaging into our applications. With this talk we hope that the term 'decoupling' gets a new, broader, meaning. Sobre Alvaro Videla Álvaro (@old_sound) trabaja como Developer Advocate para RabbitMQ/Pivotal y es coautor del libro RabbitMQ in Action Meetup: https://www.meetup.com/PHPMad/events/220122617/ Twitter: https://twitter.com/phpmad Nos vemos en PHPMad...

Sin descripción.