Convert windows Delphi app to web based app with SQL database - host in cloud

[TMasterMind]

Hi All,

A friend of mine has a windows application that was developed in Delphi and runs off an SQL database(2008/2012). How does she convert the application to be web based and hosted in the cloud? This app is basically a metering system for reporting on electricity and water for customers.

Any recommendations for companies that can convert this to cloud and host as well?

Thanks

 

[Spacerat]

Hi All,

A friend of mine has a windows application that was developed in Delphi and runs off an SQL database(2008/2012). How does she convert the application to be web based and hosted in the cloud? This app is basically a metering system for reporting on electricity and water for customers.

Any recommendations for companies that can convert this to cloud and host as well?

Thanks

Complete rewrite unfortunately.

You could migrate the local SQL DB to Azure SQL and then hook the Delphi app up to the cloud DB. But will be much slower. Depending on how complex it is you can do a lot with Azure functions to implement WebAPI. If it was developed in .NET it is much easier moving to MVC. But Delphi teaches very bad habits in terms of architecture (not saying it is the case here). But plan and budget for a complete rewrite. Get someone that understands modern application architecture. PM me if you have questions.

 

[ArtyLoop]

Complete rewrite is necessary.

Depending on how complex it is you can do a lot with Azure functions to implement WebAPI.

That sounds like a horrible hack

 

[Spacerat]

Complete rewrite is necessary.


That sounds like a horrible hack

Not really, have a look at Azure functions. MS themselves suggest that you can replace a WebAPI with functions. It is actually pretty awesome. Pure server-less and stateless and you pay per use only.

I am currently doing an IOT solution where Azure functions process the hot-path and push out to clients via websockets. Obviously all the real processing is done with my own pipeline. The point being that the Azure function triggers your own processing.

Functions do not (yet) give you all the niceties of WebAPI. WebAPI controller supports DI whereas Functions not yet.
Functions do not yet fully support .NET Core

If your controller is completely stateless then it is a good candidate for Functions. Functions focus on your implementation without having to do any plumbing code. The tooling is a bit finicky still.

 

[TMasterMind]

Thanks for all the responses. A rewrite would be best I think so too.