DWKit — a modern .NET Core platform

Introduction

Historically, there were two key issues in the .NET world:

1. Applications could not run on Linux (statistically, 38.3% of all websites run on Linux);
2. There were no affordable BPM platforms.

The world has changed.

In 2016, Microsoft released the first version of .NET Core that allowed to run .NET applications on Linux. Everyone expected the migration of existing .NET Framework-based applications to be trivial. In reality, the migration had significant problems and most of the products did not migrate remaining Windows-locked.

In 2018, OptimaJet released DWKit, a .NET Core-based BPM platform. The platform is intended for the development of enterprise applications and cloud services, and supports MS SQL Server and PostgreSQL. This allows customers to use both Windows and Linux.

Licensing model

Licensing models with recurring payments dominate the BPM systems market. It might be handy in some scenarios, but most of the time the customers overpay.

DWKit has a perpetual license. In other words, you need to pay once and then you can use DWKit as long as you like.

DWKit’s SaaS license has no limitations on the use of applications created with DWKit except for when such an application is distributed as a development platform.

Technologies

DWKit is developed with the use of contemporary technologies. When starting project development with DWKit you can be sure that it won’t become obsolete.

DWKit uses React/Refux, SemanticUI, ChartJS, Konva, JavaScript, HTML, CSS and Webpack in its frontend, and .NET Core (C#), Newtonsoft.JSON in its backend.

We do not utilize technologies that can put limitations on the use of your product.

Risk management

The key task of a manager is to manage risks. Here are the key risks technical managers face:

№	Risk	Probability	DWKit’s response
1	Not meeting deadlines	High	A ready-made user interface; DWKit application templates; Mature architecture—no need to alter it; Vendor technical support
2	Overbudget	High	Possibility of having short iterations between releases; Mature architecture—no need to alter it; Flexible licensing model
3	Unpredictable quality	High	A ready-made user interface; Minimal terms for PoC and MVP delivery; Contemporary technological stack; Possibility of having short iterations between releases
4	Increase of technical debt	High	Mature architecture; Ready-made documentation; Vendor technical support and updates
5	Little experience and poor qualification of the team	Medium	Mature architecture; Ready-made documentation; Vendor-made samples
6	Key employee leave	Medium	Mature architecture; Ready-made documentation; Vendor technical support and updates

Conclusion

By the beginning of 2018 .NET is fully matured to be used in production. We are sure, that the popularity of .NET Core will grow further. Developers will migrate both .NET Framework-based projects and projects based on other technologies to it. This task has become easier with the release of DWKit.

DWKit lowers time to market and ensures the predictability of quality and budget. The access to the entire source code gives you full control over the project and ensures you are vendor-unlocked.

Begin your DWKit endeavor with getting acquainted with the Demo and reading the ‘Get started’ guide.