We support the classic ASP based web application, using VBScript as the main language. We agree that our backend (framework, if you wish) is outdated and does not provide us with the right tools to quickly move forward. We have largely adopted the current webMVC pattern, which is everywhere, and cannot do it in a reasonable way using current technology. The big missing features are proper dispatching and inheritance patterning, among others.
Two ways are currently being discussed:
- Transfer the existing application to Classic ASP using JScript, which allows us, I hope, to switch from there to .NET MSJscript without any problems and, ultimately, to be on the .NET platform (it is desirable that the MVC material was done by then, ASP. NET is not much better than we were now, in our opinion). This has been proven as a safer way with less risk than the next option, although it may take a little longer.
- To completely rewrite the application using some other technology, now the package leader is Python WSGI with a custom ORM structure and a good solution for templates. There is room for maneuver for even django and other ready-made solutions. This method, we hope, will be the fastest solution, since we are likely to launch a beta version next to the actual product, but it does have a big waste of time if we cannot / do not get it right.
This does not mean that our logic has disappeared, because what we have built over the years is quite stable, as noted, it is simply difficult to handle. It is built on SQL Server 2005 with heavy use of stored procedures and published on IIS 6, just for a bit more background.
, . - ? , , .. , .