Better compose/organize/design pattern for all asp.net core developer

Now your are working on minimal APIs , but as an developer for doing a complex/big web application, that I will never ever to use it.
because we need a better and better compose/organize pattern for separate out project, sound familiar ？ yes , Micro service, but not every app can/should use Micro service， and In fact , Micro Services are also need great compose/organize pattern for project, and This is why Java so popular in Web, the Apache Foundation create “Spring” and other “Spring Family” for Java, and with that , more design pattern and design concept are goes to every Java web develper’s mind. with that , they write many architecture book/blog , and that make their community keep innovate （because the mind of DDD and implementation make them stop DRY (Do Not Repeat you self), they can do more with less, and many common component are release to maven, and share to everyone , and the new developer can use those maven packages as business components to simplify their mork ). But what about .Net ? the official way that from asp.net core team is to create a template with dotnet new , and to share your business components is to copy and past your code, Nuget can only bring “provider” packages like (database provider, authentication provider, rabbitMQ provider etc.) There are some company (like Volosoft’s ABP) try to bring the same thing for .Net too, but after all , they are Commercial project (but free) and third party do not have the Influence , that means, there business components can only be used in there ecosystem.

I wasn’t happy to see .net keep releasing those “toy or demo” apis when minimal APIs was released. why? Less code is more learn and more work to repeat.

So to bring every developer in Asp.Net Core ecosystem, the Asp.Net Core team should release a great compose pattern to help us to share our business component across different web services , that may contains virtual file system , modularization , isolation ,generic AOP and many other (and current feature like MVC/SignalR should optimize for that) .

Most importantly , to tech better design architecture/mind/concept for everyone inside asp.net core ecosystem . (Ps. the doc of best practice , for this, we should learn from Angular’s document, not just about how to use, but also how to use it better)

[davidfowl]

Convey - a simple recipe for .NET Core microservices

I love this framing, it’s recipe, not a framework. It’s made up for lots of packages from nuget that exists today. IMHO the docs that are scenario specific are much more helpful that the framework itself. I don’t see what it adds over the core framework beyond the curation of these packages and that’s something we should definitely do more of.

[davidfowl]

You need to use non MS FOSS to build anything real and the .NET team does not want to be the one stop shop for everything, that kills innovation in the OSS community and we already get flack for that. .NET developers need to reconcile that fact, we’re not going to build everything. This is why we’re sticking to building primitives that others can build on.