Communication - queue

[marcotroisi]

I think that we could use a queue system to handle communication between microservices. RabbitMQ is a great fit in my opinion.

It seems to me that the alternative to this is using raw HTTP between microservices.

What are your thoughts?

[luigizuccarelli]

@marcotroisi - I agree on queing and also caching - why not consider redis as part of the poc ?

[marcotroisi]

Great idea! We could do two PoC, one with Redis and one with RabbitMQ, between the two us.

We just need to think of a few "guidelines" so that we build something similar and we don't compare apples to oranges.

What do you think?

[luigizuccarelli]

yes absolutely , I quite like the mediator pattern that the guys have adopted for the raincatcher front end , its more like the talk we had at meetup, the ms will send messages and if there are other ms or consumers that listen to messages and the topic is related they use it - nice and clean

[marcotroisi]

I like that too a lot

On Fri, 31 Mar 2017 at 09:33 Luigi Zuccarelli ***@***.***> wrote: yes absolutely , I quite like the mediator pattern that the guys have adopted for the raincatcher front end , its more like the talk we had at meetup, the ms will send messages and if there are other ms or consumers that listen to messages and the topic is related they use it - nice and clean — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaOwA3wWpZWpqSRv6F82TwvMCHR28KFks5rrLpFgaJpZM4Muhq8> .

-- @marcotroisi <http://www.twitter.com/marcotroisi> | www.marcotroisi.com