PHP AMQP VS Moleculer

I installed rabbitmq succesfully and went through the tutorials without trouble: http://www.rabbitmq.com/getstarted.html

Microservices have nothing to do with Nest vs Express or anything like that. It's really just about breaking your code into smaller services and then using a mechanism to communicate between them. Hell, you can even have one service using Nest and the other Express if your communication mechanism is HTTP. A more robust system typically uses something like RabbitMQ, which allows for different types of messaging patterns and asynchronous messaging.

One day I was trying to learn the deep concepts of RabbitMQ, its use cases and why it's different from other message brokers. I've started by reading the cool documentation and then I was eager to try it out in a demo application.

Having said that, RabbitMQ has wonderful tutorials, and a lot of effort has gone into making it accessible for newcomers. Here you go: https://www.rabbitmq.com/getstarted.html

I'm not going to explain every argument of the called methods. If you want to better understand each of them, take the RabbitMQ tutorial. It's pretty simple and will give you all the information you need!

If you are not familiar with RabbitMQ or the streadway/amqp driver, you can try it out using the official tutorials. Just replace any "github.com/streadway/amqp" import statements with "github.com/peake100/rogerRabbit-go/pkg/amqp". If you find a tutorial this does not work for, please open a PR!

My goto for this kind of task is moleculer: https://moleculer.services/

Fast, battle tested, vue2-like approach, great documentation, good community. The automatic indipendent-scalability as an option is usually the main selling point of these solutions, but honestly I think the real pro is the "composition" approach, which is essential if you want to keep a clean and well-organized codebase. On this regard, I found moleculer pretty great even for large teams.

If you’re using k8s, check out https://moleculer.services and this would likely solve what you’re looking for.

Molecular – Progressive Microservices Framework for Node.js

While you’re delving into microservices, check out Moleculer https://moleculer.services

I almost can’t believe I haven’t seen it mentioned here before, but adding Moleculer into your node project (if it’s clustered/k8s’d) will literally solve many single threaded problems, not to mention tons of other scalability issues. https://moleculer.services/

You could use a framework for this. Have a look at moleculer

I haven't used this, but it seems neat: https://moleculer.services/

Look into Moleculer.

Moleculer already provides an in-house http gateway, but what if you want to use an existing API, and how to maintain decoupled code when creating your gateway? This package solves both. You can create your API, passing in any services you require as dependencies. You can then bind your API to moleculer using the moleculer-universal-gateway.

But there's more to the topic of microservices. Seems like all the conversation focuses on deployment pain. You can build a service with something like Akka or Moleculer where the modules act independently and have some message passing and resilience from each other, but they can still all live in one codebase, one process, and deployed as one unit. It works fine and isn't painful at all. And maybe down the line you decide to split the thing up into multiple processes and multiple deployment units, and that's an easy refactor because the modules are already somewhat separated.