Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Add documentation on how to communicate between two applications #396

Closed
arschles opened this issue Jul 21, 2016 · 5 comments
Closed

Add documentation on how to communicate between two applications #396

arschles opened this issue Jul 21, 2016 · 5 comments
Assignees
@bacongobbler
Labels
docs

Comments

@arschles
Copy link
Member

Given that Deis is a platform well-suited for running microservices, we should include documentation on the best way for microservices to communicate. As of now, we're saying that DNS is the best way to do so.
@arschles arschles added the docs label Jul 21, 2016
@arschles arschles added this to the v2.3 milestone Jul 21, 2016
@onbjerg
Copy link
Contributor

onbjerg commented Jul 22, 2016

Amazing. This is just the answer I was looking for, and then it's the first issue on GitHub.

Is DNS in Deis the same as DNS in k8s?

@bacongobbler
Copy link
Member

Sorta. We're referring to how two applications communicate, and that would be through the router. We eventually want to get to the point where an application can discover it's own processes which will be through DNS but that is not available at the moment.

@onbjerg
Copy link
Contributor

onbjerg commented Jul 23, 2016

Oh, alright. Thank you for the swift answer.

@vdice vdice removed this from the v2.3 milestone Aug 3, 2016
@bacongobbler
Copy link
Member

We now have a blog post on how two apps communicate. I can write up a little blurb in the docs about it.

@bacongobbler bacongobbler self-assigned this Oct 12, 2016
@bacongobbler
Copy link
Member

closed via #723.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bacongobbler bacongobbler

Labels
docs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@arschles @bacongobbler @onbjerg @vdice