Bring reference architecture up to date

[WestDiscGolf]

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

This reference architecture is really interesting but as with the ever increase in cadence of functionality in Azure it has fallen behind in services, SDK versions, best practices etc. and not been updated for 2 years. It would be really helpful if this reference architecture was updated to work with the latest functionality in Azure Functions etc. and best practices as required.

Thanks!

[lockhartsoftware]

Yes please. That’s a excellent idea.

[joelhulen]

I would love to update this because I agree on all points. I need to check with the stakeholders, including @gk-8

[jongio]

Any update @joelhulen?

[joelhulen]

I've not heard back from @gk-8

@jeffhollan Do you have any insight on how we can update this?

I'll send an email to the team to see if we can get this going again. I'm glad to see the interest!

[lockhartsoftware]

In my opinion, this is the single best resource that I have discovered on how to design and build a Serverless microservices application using Microsoft Azure. Believe me, I have wasted hours checking out various other resources, and nothing comes close.

I really appreciate the hands-on, detailed walkthrough approach to learning.

Not only do you show the ‘how’, but you also explain the ‘why’.

I have already used this reference architecture in a number of my designs, with great success I might add.

This reference architecture really is an exemplar, and should be the approach taken by Microsoft across all of its technologies.

Please update.

@jeffhollan
@joelhulen
@gk-8

[jeffhollan]

Thanks all for flagging - let me circle back with the team and see if we can get someone to spend some cycles here

[joelhulen]

Thanks, @jeffhollan! Please feel free to reach out to me if you want some help.

[lockhartsoftware]

Could we make the frontend Blazor WASM this time, please? That would be just perfect!

[rohannevrikar]

I completely agree with @lockhartsoftware! I still come back to this repo to understand best practices while using Azure serverless, and I've personally learnt a lot from this resource. I'd love to contribute if things move forward.

[joelhulen]

@lockhartsoftware I would actually like to do a WASM version this time around. As much as I love Vue, which I enjoyed using in the current version, I've recently started using Blazor WebAssembly and it's an absolute joy to use. Now I just need the blessing from @jeffhollan to update this architecture 🙂

[WestDiscGolf]

A blazor wasm ui sounds like a good plan to me. As the ui is a small part of the architecture then maybe the community can contribute other ui framework versions maybe if its wanted?

[lockhartsoftware]

@joelhulen building interactive web UIs using C# instead of JavaScript is, in my opinion, sheer bliss. I spent the last 3-4 years with Angular on the client-side, and now with Blazor WASM I believe that my productivity has spiked significantly.

Oh, go on @jeffhollan, you know it makes sense 🙂

[lockhartsoftware]

@joelhulen @jeffhollan Hello! Any update on this? Thanks.

[jongio]

Adding @JasRobe to the issue.

[lockhartsoftware]

Excellent. Thanks @jongio I look forward to seeing the outcome of your work.