We are keening to implement our system as microservices and see that you have the road map to implement 'startup template to create microservices'? in the ABP Commercial. It would be great for us having that since we don't have to do services splitting and service comminication ourself.
So, we keen to know the estimted timeline for the feature release date, please.
4 Answer(s)
-
0
Hi,
This is one of the high priority items in our road map. However, there are some other important items too (like Blazor UI and .NET 5 upgrade). Creating a microservice template is not a trival work. I can't write an exact date, but you can think it like end of 2020 or beginning of 2021 (so, in 3-5 months range).
-
-1
Since my own ticket got redirected here I'll suppose I'll add my thoughts here too.
How can you possibly think it's a good idea to prioritise a blazor UI preview or .net 5 beta upgrade before ensuring your paid commercial package has the same feature level as the free platform.
Neither blazor or .net 5 are production ready, just previews.
If creating a microsservice example is not trivial work then exactly how are we supposed to do it!?
-
0
Hi,
Blazor is production ready & stable. I didn't understand why you thought like that. We will work on the .net 5 when it close to release, so we publish a .net 5 compatible version short time after its final release (we need to prepare for it).
We are not making Blazor only for the free side. We will do it in parallel with the commercial one.
ABP Commercial features are already much more than the free framework, because all the free features are also available to you and ABP commercial already has many more modules/themes/tooling etc.
If creating a microsservice example is not trivial work...
I suppose there is a misunderstanding. I've written "microservice template", not "microservice example". Example is already available (see it) and documented, so you can develop your ms solution by inspiring from it. If you think that it is for free side, no, there is no diference, you can make the same with the ABP Commercial.
But it is an example, nota startup template. Once you can understand this example and the ABP Framework in overall, you can build your own empty microservice solution in a few days or less (create empty microservices, arrange all the environment, gateways, caching, event bus... etc).
Creating a template is something different, on the other hand. We document templates, we develop tooling (CLI/Suite), we prepare CI and other internal environment and do a lot more stuff to create a new solution using the template, generate source code on this new template structure, add modules to the template.
In addition, microservice is a different thing.. We want to add CLI/Suite features to "add a new microservice to the solution" that auto configures all the clients, gateways... to make this ms work. There are a lot more.
So, creating your solution for your own is much more simpler than our work.
I know, every one see his own requirement is the most important one. But we get feedback from thousands of developers. And Blazor is far more most wanted feature than others. Just see the attraction: https://github.com/abpframework/abp/issues/394 Can you show a similar demand about the microservice template?
I don't say microservice template is not important. I've written "This is one of the high priority items in our road map". However, even if we start it today with full energy, you can't expect it to be production ready before ~2 months. So, 3-5 months should be reasonable.
-
0
Yes I was really asking for just a fully working/best practice example of the microservice project integrated with the commercial modules. This may be different to what the OP was requesting so feel free to reply to the other question.
Personally I don't see Blazor being heavily used in real projects for several years. Maybe thats not the case for the free users on github.
