-
Notifications
You must be signed in to change notification settings - Fork 9
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
Flomesh + Dapr blog duplicate #100
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
Signed-off-by: Nick Greenfield <nigreenf@microsoft.com>
Azure Static Web Apps: Your stage site is ready! Visit it here: https://thankful-ocean-0d6f6e61e-100.westus2.azurestaticapps.net |
@naqvis - please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @hhunter-ms
|
||
The diagram below demonstrates how Dapr and Flomesh service mesh can be integrated to enable cross-cluster service communication. The example consists of two components: a server-side NodeApp and a client-side curl. | ||
|
||
The server-side NodeApp is a Dapr application, modified from the NodeApp in the [Dapr hello-kubernetes](https://github.com/dapr/quickstarts/tree/master/tutorials/hello-kubernetes) tutorial example. When it returns a response, it displays the name of the current cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you provide a link to the modified code repo also, so that people can then see/try out the modified code example?
Actually, now I see it is here https://github.com/addozhang/flomesh-dapr-demo/tree/main/nodeapp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@naqvis ^^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do I still need to update the doc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't look like it! I'll add the link Mark found
Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
Azure Static Web Apps: Your stage site is ready! Visit it here: https://thankful-ocean-0d6f6e61e-100.westus2.azurestaticapps.net |
Thank you @hhunter-ms for all of the support and help. I have reviewed the blog post at stage site https://thankful-ocean-0d6f6e61e-100.westus2.azurestaticapps.net/ Please advise If any further action from my side is required to get it published to Dapr blog? |
@naqvis the other maintainers are reviewing, but so far the feedback is confusion around the diagram showing Redis( |
Redis in that diagram (external to clusters) is the component which shows how to do cross cluster Dapr state management and is not required or mandatory for cross cluster service calls. We can have this component removed from the diagram if its causing confusion. So technically speaking, all cross cluster calls are done without any need of state management, and we can have Redis safely removed from diagram. |
Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
Azure Static Web Apps: Your stage site is ready! Visit it here: https://thankful-ocean-0d6f6e61e-100.westus2.azurestaticapps.net |
@msfussell it sounds like we're waiting on an additional reviewer from a maintainer on this - is that right? @artursouza, @berndverst, @yaron2 could one of be a second pair of maintainer eyes to get this reviewed? |
Any update please? |
No description provided.