- Aron Cox
- PowerServer
- Tuesday, 9 November 2021 12:55 PM UTC
Let's say I am a small software house. I have an old client-server application that I want to modernise. I think turning it into a web-based application makes sense because then my years of carefully built business logic can be called by anyone.
I believe this is the idea behind PowerServer, the newer version of which requires conversion of the business logic code to C# so it can be served up via a Rest API using standard tools, like IIS. I understand the conversion is now automated and pretty simple thankls to the .NET datawindow.
Does that sound right?
If so, then let's assume I have 10 customers, 5 of which are large with hundreds of users, but 5 of which are small with less than 10 users. No-one wants their data to be in the cloud, it has to be local, and therefore the right architecture seems to be to also have local PowerServer servers.
Does this mean each customer needs a PowerServer licence? The cost for the smaller customers would be pretty prohibitive, and means we couldn't change our architecure, as that would require buy-in from all customers?
Does that sound right, or am I missing something? For example is there a licence type that lets us purchase it and then use PowerServer wherever we like? Or wherever we like for a single application suite or something?
Thanks for your help.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.