5

I am creating a service to be exposed on the internet. One of those things you would normally say "Web 2.0", but that I want to expose as a SOAP webservice, with desktop clients.

I know that it may sound a little bit outdated, but despite the apparent "uncool" factor, is there any real reason why this approach shouldn't work?

Yes, I will buy a VPS for this thing, it's an experiment for now - but who knows the future.

I am just wondering, well, what you think of it :)

Andrea

2 Answers2

4

The only weakness I see to your approach Andrea, is that the deployment of the application is harder. What if you need to install in 100 PCs, and then you need to upgrade the application, and then the program stops working in 3 of these PCs, etc.

For the previous reasons, if your software functionality can be implemented in a Web Application, I would definitely be headed in that direction.

Marcelo
  • 619
3

A lot of applications have been built this way and still get built this way. It's been proven to work and can be very reliable and secure. We've built a number of desktop applications this way and have had a lot of success with it. And given the right circumstances, I'm sure we would do it again.

Ali
  • 211
  • 2
  • 8