docs/en/Blog-Posts/2020-01-15 v2_0_Release/Post.md
ABP Framework v2.0 has been released in this week. This post explains why we have released an early major version and what is changed with version 2.0.
In addition to the v2.0 release, we are excited to announce the ABP Commercial, which is a set of professional modules, tools, themes, and services built on top of the open-source ABP framework.
It was planned to release v1.2 after the v1.1.2 release. However, it is reported that v1.x has some performance and stability issues on Linux, especially when you deploy your application to Linux containers with low CPU and memory resources.
We have investigated the problem deeply and have seen that the root cause of the problem was related to the implementation of intercepting async methods. Besides, there were some async over sync usages that effected the thread pool optimization.
Finally, we solved all the problems with the great help of the community. But we also had some important design decisions which cause some breaking changes and we had to change the major version number of the framework because of the semantic versioning.
Most of the applications won't be affected by the breaking changes, or it will be trivial to make these necessary changes.
Some of the interceptors are required to use async APIs. When they intercept sync methods, they need to call async over sync. This eventually ends up with async over sync problem. That's why we have removed some sync APIs.
Async over sync pattern is a classical problem of C# when you need to call an async method inside a sync method. While there are some workarounds to this problem, they all have disadvantages and it is suggested to not write such code at all. You can find many documents related to this topic on the web.
To avoid this problem, we have removed:
sync repository methods (like insert, update, etc...),sync APIs of the unit of work,sync APIs of the background jobs,sync APIs of the audit logging,sync APIs.If you get any compile error, just use the async versions of these APIs.
Beginning from the v2.0, the ABP framework assumes that you are writing your application code async first. Otherwise, some framework functionalities may not properly work.
It is suggested to write async to all your application services, repository methods, controller actions, page handlers.
Even if your application service method doesn't need to be async , set it as async , because interceptors perform async operations (for authorization, unit of work, etc...). You can return Task.Completed from a method that doesn't make an async call.
Example:
public Task<int> GetValueAsync()
{
//this method doesn't make any async call.
return Task.CompletedTask(42);
}
The example above normally doesn't need to be async because it doesn't perform an async call. However, making it async helps the ABP framework to run interceptors without async over sync calls.
This rule doesn't force you to write every method async . This would not be good and would be tedious. It is only needed for the intercepted services (especially for application services and repository methods)
See the release notes for the other breaking changes. Most of them will not affect your application code.
This release also contains some new features and tens of enhancements:
Volo.Abp.AspNetCore.Serilog package.C# client proxies.Async background jobs.DeviceFlowCodes and TokenCleanupService for the IdentityServer module.See the release notes for the complete list of features, enhancements and bug fixes.
We have completed some missing documentation with the v2.0 release. In the following weeks, we will mostly focus on the documentation and tutorials.
ABP Commercial is a set of professional modules, tools, themes, and services built on top of the open-source ABP framework.
In addition to these standard set of features, we will provide customer basis services. See the commercial.abp.io web site for other details.
The ABP Commercial is not a paid version of the ABP Framework. You can consider it as set of additional benefits for professional companies. You can use it to save your time and develop your product faster.
ABP Framework is open source & free and will always be like that!
As a principle, we build the main infrastructure as open-source and sell additional pre-built application features, themes, and tools. The main idea similar to the ASP.NET Boilerplate & the ASP.NET Zero products.
Buying a commercial license saves your significant time and effort and you can focus on your own business, besides you get dedicated and high priority support. Also, you will be supporting the ABP core team since we are spending most of our time to develop, maintain and support the open-source ABP Framework.
With the introduction of the ABP Commercial, now ABP becomes a platform. We call it as the ABP.IO Platform which consists of the open source ABP Framework and the ABP Commercial.
If you are wondering how exactly looks like the ABP Commercial application startup template, you can easily create a demo and see it in action. The demo includes all the pre-built modules and the theme.
Here, a screenshot from the IdentityServer management module UI:
This is another screenshot from a demo application using the material design style of the theme:
You can build unlimited projects/products, sell to unlimited customers, host unlimited servers without any restriction. Pricing is mostly based on the developer count, support level and source code requirement. There are three main packages;
See the pricing page for details. In addition to the standard packages, we are also providing custom services and custom licensing. Contact us if you have any questions.
The license price changes based on your developer count, support level and source-code access.
Team license doesn't include the source-code of the pre-built modules & themes. It uses all these modules as NuGet & NPM packages. In this way, you can easily get new features and bug fixes by just updating the package dependencies. But you can't access their source-code. So you don't have the possibility to embed a module's source code into your application and freely change the source-code.
Pre-built modules provide some level of customization and extensibility and allow you to override services, UI parts and so on. We are working on to make them much more customizable and extensible. If you don't need to make major changes in the pre-built modules, the team license will be ideal for you, because it is cheaper and allows you to easily get new features and bug fixes.
Business and Enterprise licenses allow you to download the source-code of any module or the theme when you need it. They also use the same startup template with the team license, so all modules are used as NuGet & NPM packages by default. But in case of need, you can remove the package dependencies for a module and embed its source-code into your own solution to completely customize it. In this case, upgrading the module will not be as easy as before when a new version is available. You don't have to upgrade it, surely! But if you want, you should do it yourself using some merge tool or Git branch system.
ABP Commercial license is perpetual, which means you can use it forever and continue to develop your applications.
However, the following services are covered for one year:
If you want to continue to get these benefits, you can extend your license period. Renewing price is 20% less than the regular price.
Just like the previous year, we are a partner of the famous software development conference: NDC London! In the previous year, we were there with the ASP.NET Boilerplate & ASP.NET Zero theme:
This year, we will be focusing on the ABP.IO Platform (The Open Source ABP Framework and the ABP Commercial). Our booth wall will be like that:
If you attend to the conference, remember to visit our booth. We would be glad to talk about the ABP platform features, goals and software development in general.
If you are in London and want to have a coffee with us, we will be available at February 1st afternoon. @hibrahimkalkan and @ismcagdas will be there.
Just write to [email protected] if you want to meet :)