3 ms·
I don't have experience with GraphQL or other graphing APIs but I do have experience with micro services written in Scala using a RabbitMQ backend and running i
by djsumdog 9y ago
I don't have experience with GraphQL or other graphing APIs but I do have experience with micro services written in Scala using a RabbitMQ backend and running in Docker containers on DC/OS (mesos).
We were experimenting with some other tools back on that projects and were looking at migration paths. If you're starting from zero, I'd recommend looking at Kafka. It's a true pub/sub model and you can use it easily to communicate with various services.
RabbitMQ is good for things that are unreliable and you don't care about data loss. We did care a lot about data loss and had to deal witreliable transfers (like SMS/text messages) there are better solutions like ZeroMQ. Avoid RMQ if you can is what I'm saying.
I'd personally recommend a backend like Kafka and writing your services in a language you like and are comfortable with. Write strong, solid test cases. With good unit tests and integration tests, language choices become less of an issue.
Also take a look at event-source for persistence. You can use regular old relational databases if you have an event sourcing micro service you rely on to persist information.