I am the current maintainer of Stylus. The Stylus library has been flagged as malicious lib, which has caused many lib and frameworks that depend on Stylus to fail to install. Please help me retweet this msg in the hope that the npmjs official team will take notice of this issue
What are competing consumers?
Let's break down this common messaging pattern.
Two consumers are listening to the same queue.
The first consumer to retrieve the message wins.
Since we can't read the same message more than once.
This is how queues work, so nothing out of the ordinary.
Now let's say you don't want this to happen.
How can both consumers get the same message?
I know, we'll just use another queue.
But... This complicates the publishing side.
We now have to publish to both queues - this won't scale.
Back to the drawing board.
You might be thinking, 'Am I using the wrong component?'
I'm glad you asked!
The solution is to use a topic.
We can connect the topic to our queues, so it will push the message to both.
And we can continue scaling this by adding more queues.
The best part?
On the producer, we can just publish to the queue.
Hope this helps!
Resilience in .NET? Polly is probably your first choice.
And Polly is much faster in V8.
But why should you care about making your application resilient?
Let's say your services communicate by sending HTTP requests.
HTTP requests are susceptible to failures from network or server issues.
These failures can disrupt service availability, especially as dependencies increase and the risk of cascading failures grows.
Here's how you can solve this: https://t.co/xazPjKwhpl
Do you use Polly in your applications?
---
Do you want to simplify your development process? Grab my free Clean Architecture template here: https://t.co/j8Z77G1HKN
Aftermovie : Insider Dev Tour Lyon. C'était énorme ! Merci à tous pour votre participation ! Merci aux speakers Microsoft et aux MVPs venus de loin pour nous régaler lors de cette superbe journée #InsiderDevTour#InsiderDevTourLyon#MVPBuzz#Office365Dev IDTLyon c'était ça :
"Atelier Coding for Children (6 à 14 ans)" avec @aymericw@vThavo @EdwigeSeminara @etienne_bailly à l'Insider Dev Tour Lyon 26 juin 13h30
Important : Inscriptions séparées pour l'atelier Coding for Children à ce lien : https://t.co/GOLwMUTmcC
#InsiderDevTourLyon#Coding4Children
Insider Dev Tour débarque à Lyon - 26 juin 2019 - Tour Part-Dieu. Inscription sur https://t.co/fzCbiZKDnA
Événement Microsoft à destination des développeurs #Microsoft365 (Windows, Graph, Office, Teams, IoT, .Net Core, PWA, Back from #MSBuild). #InsiderDevTour#InsiderDevTourLyon