I was curious, what other architectures exist for business or user focused development that aren't written using web applications. Are these architectures used today?
If you are or were in the business world and you need to connect to an application from a remote location, what technology would you use (that isn't web application based)?
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
There are plenty of applications out in the business world today that use fat winform type client where the data for the application is remote.
Most common method today for a business user to connect remotely is through VPN. The connections these days are actually quite fast. While there is a small delay accessing any data or file shares, it is manageable.
While not as popular as VPN. Virtual desktops are pretty awesome. A virtual desktop basically allows you to connect to a computer in your office from any other computer that has internet access. Once you make the connection, the speed is the same as if you were sitting right in the office.
VNC, Cytrix (Windows only), Windows Remnote Desktop, or how about plain old X over SSH. All of these require no customaisation of the user appliactions to remote working, some require lower bbandwidth than otehrs, and X programs written by Windows developers tend to need a low latency and high bandwith. Theres other technologies out there, but your question needs to be a bit more specific to consider them.
Well, the first thing I would do is use SSH to connect to a shell on a remote server. If you're talking about software for the general non-geeky population, then it might be different.
It depends on what your remote application is suppose to do for you.
These days everybody talks about making RESTfull services to access remote databased services, and web interfaces for remote applications. But it depends what kind of service this remote application is suppose to do for you.
If its an application which a local application should talk to it depends on the interface of the remote application. For communicating across computer boundaries there are different frameworks which claim to help you, if you are using .NET it could be WCF for example.
WCF is a pain in many aspects, but also provides you with a lot of functionality out of the box.
So my bit for an answer is "it depends" :)
Having worked with it for quite a while, I'm a keen user of the CORBA middleware framework for distributed apps. It's not very popular in general though for a number of good reasons:
I know it's still used extensively in the financial sector, at least, for in-house distributed systems. One major advantage it has over a language-specific middleware (like .NET remoting/WCF) is that it is language agnostic, and implementations exist for many different languages. That means you can implement your server interface on some ancient back-end database server in C++, and then write a client in Java or .NET which talks to it.
Other alternative, more modern middleware frameworks include ICE and Apache Etch.
Things like SOAP and XML-RPC also provide similar network service interfaces. They are a lower-level specification than the ones above, and indeed can be used as the underlying network protocol in some cases.
