Project Phoenix 🐦‍🔥

[iammukeshm]

• Organizing the entire project to an even more scalable enterprise-grade solution/framework.
• Build a real-world POS system using the fullstackhero framework.
• Writing my own Command / Query Dispatchers.
• Writing my own EventBus for Notifications and Domain Event Handling.
• Remove MediatR references.
• Replace MediatR Pipeline Behavior with Decorators / Middlewares.
• Better Exception Handling.
• Best of VSA + CA Worlds!
• I am going with NextJS this time instead of Blazor (more updates on this soon).

[kallievz]

Good Morning.

Will the Blazor UI still work after all these changes to the backend service?

[iammukeshm]

Good Morning.

Will the Blazor UI still work after all these changes to the backend service?

Hi, yes the Blazor UI should still work. However, I am planning to build a POS Frontend completely on NextJs. Maybe I can build a dashboard app on Blazor as well.

[maxiar]

Hi! You Refactor the frameworks again? v3? Good news :) .. I hope really want to show a complete framework including EventBus Messages, Microservices and Next.JS. A Complete framework in All in One Repository.. This template is very usefull for the community. Good Luck!!

In other hand, how are planned replace/add the MediaR and MassTransit (they will be comercial) ...? May be wolverinefx (https://wolverinefx.net/tutorials/from-mediatr.html), WolverineFX appears the natural lib to support both frameworks, mediators and message broker (with RabbitMQ)? , to avoid reinvent the whell and dedicate your limited time to another parts from the framework... What is your opinion? Thanks in advanced!

Another question, what motivate the new Project Phoenix, after a long period without any updated? Did you use this in the next solution or .NET courses?

Regards!

[maxiar]

Hi @iammukeshm ! great job.. any estimated ETA?

[kallievz]

Hi @iammukeshm ! great job.. any estimated ETA?

Same, just waiting for the next push, want to see the inter-module communication implementation. Would be of great help.

[iang0ld]

@iammukeshm, I loving this move away from mediator and embracing of vertical architecture.

Two thoughts.

1. Should infrastructure be a module or separate as in version Reasoning is that it contains cross cutting concerns and is used differently to a module. Program.js supports this thought with the separation of the two lines:

app.ConfigureFshFramework();
app.ConfigureModules();

2. Should request and responses be together with the other feature files rather than separate. Keeping them separate seems to go against the idea that vertical architecture keeps all files for a feature in one place.

[kallievz]

Any new changes to Project Phoenix, anything need help with?