Thank you

[pascalandy]

Here is the place to say thank you to folks who are working hard on this project.

« One of the greatest ways to show your appreciation to open source projects you enjoy is to open an issue that let people say thank you »

Disclaimer: I don't have any kind of connexion or personal interest with maintainers(s) of this project. Pure gratitude here.

Cheers!

[BretFisher]

You are most welcome!

[pascalandy]

This is more than awesome! You rock Bret :-p

[BretFisher]

Thanks, I'll get to do this session at DockerCon EU in December and also adding more to http://swarmmastery.com using this repo so expect some more updates in 2018

[pascalandy]

For me, the big highlight in your stack is the RexRay docker volume plug with DigitalOcean storage. I looked for an example for ages!

In your ToDo, I saw that you are looking to setup socat. Here it is!

[BretFisher]

Yea we need to start adding todos to GHIssues not hidden in my code. I'll start that.

[bradschafer]

Thanks for this amazing repo.

I've used your 'good node defaults' for some time now.

Although I am more a 'dev' than 'devOps' I am embedding myself into learning the Cloud Native stack and tossing many assumptions along the way.

Your Docker course on Udemy was great and the direct correlation to code and repo's is always straightforward and well organized.

If you haven't looked at NEST JS yet, it's likely worth a look as I see it changing how we approach node in the microservices age.

I am looking forward to getting a rex-ray swarm running as persistance has always been the gaping hole in all this.

I also didn't see any 'message queues' in the pattern mix (but I haven't dug super deep into all the stacks yet), is this by design?

Lead on captain!

[BretFisher]

Thanks @bradschafer I'm glad it's all helping!

I'll check out nest.js, thanks. As for message queues, I'm not sure what you're looking for. In the voting stack, redis acts as a queue for the worker service to process votes and then store them in postgres. I don't see anything necessarily special about message queues as part of a distributed system that would warrant a special stack for them, so feel free to ask the question a different way if you're thinking differently.