Eshoponcontainers: eShop port to Dapr (in-progress)

[kalasp]

Are there any thoughts or initiatuves ongoing to port eShopOnContainers to Dapr (http://dapr.io)?

[nishanil]

Yes, we are in plans for doing a POC on it first. At present, we are wrapping up a few things with .NET Core 3 updates I'll update this thread when we will start to work on it.

[ArashSade]

Really? Spend time on something that is still on alpha phase?

In addition, wouldn't it make more sense for the contributors of the dapr project to make this POC?

NServiceBus has done the same.

[nishanil]

Sorry if it sounded like we are jumping on it right away 😊.

One of the top feedback that came in from the survey that we did in Feb is that we should work on newer cloud-native tech and update recommendations sooner. So, we try our best to prioritize techs based on the industry feedback and how a customer is embracing a particular tech. Not all POCs land into our main codebase. We gauge based on various factors and if there is a way to provide it as an optional script, we do that and update the wiki,

In some cases, like the ELK stack, we go ahead and do the POC first, and when we are totally convinced, we merge them to the code (as an optional feature) and update the documentation accordingly.

In other cases like the current code migrations to .NET Core 3.0, we worked on POCs on Service Mesh like Istio, Linkerd and also proxies like Envoy. In the next update, the codebase will be updated to support Linkerd and Envoy proxy. Again, in the case of Linkerd, it will be an optional script that you can run to Mesh the production environment. We're also working on guidance on Cloud-Native that will focus on choosing the right tech on Azure for the job. We would like to keep the eShop sample flexible to support our guidances.

Another main feedback was that the code was complex to Get Started, so we worked on to keep it simpler but also providing an option for production scenarios like k8s and service mesh. See the Roadmap

Having said that, we're open to feedback and do course corrections if necessary 😊

[mvelosop]

Closing this issue now but feel free to comment, will reopen if needed.

[Shawn-Fan]

@nishanil Will you guys rewrite "eShopOnContainers" project in actor model based on dapr in the future?

[nishanil]

No concrete plans on Dapr port yet.

[antmdvs]

Hi. With the recent coverage of Dapr at Build by Russinovich, Fussell, and team, I expected to find some work being done here to incorporate it. Can you consider re-opening or explaining why this is closed? Thanks!

[mvelosop]

Hi @antmdvs.

That's one of the topics that's being discussed now for next FY 😊

It's still a bit early to know, but it'll be announced when the time comes.

Hope this helps, at least a bit. 😉

[MedAnd]

Hi eShopOnContainers team, please consider re-opening this issue given DAPR is being proposed by Microsoft as the premier technology & pattern for micro-service and container solutions!

Ideally DAPR will unify & abstract AKS / Service Fabric and Azure Functions capabilities via the common DAPR runtime & API.

Not supporting DAPR seems at odds with the vision of also having eShopOnContainers as the premier blueprint from Microsoft for modern micro-service patterns and practices.

@mchmarny @msfussell @yaron2

[nishanil]

Hey, @MedAnd, Absolutely! Thanks for bringing this up.

We are in the process of embracing and integrating Dapr to eShop. We are also working on a new e-Book called Dapr for .NET developers. An accompanying reference sample eShopOnDapr will focus on the Dapr features specifically and will also highlight the benefits. I will reopen this issue for now and update it when we have more details to share. :-)

Adding the authors @amolenk, @EdwinVW and @robvet too!

[MedAnd]

thanks @nishanil... the Title though could do with an update 😎

[nishanil]

Just made the repo public: https://github.com/dotnet-architecture/eShopOnDapr
Please note, It is still work-in-progress 😊