Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please improve docs on best ways to do messaging on kubernetes #2

Open
kristianmandrup opened this issue Apr 27, 2018 · 0 comments
Open

Comments

@kristianmandrup
Copy link

kristianmandrup commented Apr 27, 2018

"At the moment its main function is loading some useful data from the cluster: current pod id and list of pods."

So how would you do the communication. Ppl have been asking whether to use mesh or some alternative

Please see senecajs/seneca#525

You can use seneca-mesh on Kubernetes but you lose some of its functionality.

Because seneca-mesh connects itself together, without using the kubernetes load balancers, when you do rolling updates, for example, you lose the benefit of the role since it uses load balancers to drain the traffic from one container and move it to another.

I did a lot of testing with mesh but decided that a message queue is simpler, gives guaranteed delivery, and allows you to leverage kubernetes rolling updates etc.

Can Pub/Sub be used effectively as messaging infra?? https://cloud.google.com/pubsub/

I would appreciate some example of senecaJS & kubernetes

NOTE:
I have found Fuge as execution environment for developing microservices, and it has a service discovery that emulates Kubernetes.
I would like to know from people that have had experience with seneca and had tried to use it in kubernetes if this fuge-kubernetes emulator could it be a substitute for seneca-mesh and seneca-kubernetes plugins to work with kubernetes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant