Hgeocities.com/Vienna/Stage/5614/enterprise.htmlgeocities.com/Vienna/Stage/5614/enterprise.htmlelayedx=Jĝ)OKtext/htmlCmo)b.HFri, 16 Mar 2007 12:38:12 GMTJMozilla/4.5 (compatible; HTTrack 3.0x; Windows 98)en, *=J) David Wilson-Burns, Software Consultant
Software Development quality, on time, with a smile...
the way you want it
 
 
Contact
Desktop
Enterprise
Web
Server-Side
Database
Automation
Technology
Methodology
Projects
About
 
HOME

Enterprise Applications

An enterprise application serves the needs of an entire organization. In other words, it is a single application that allows its users to interact concurrently with the same data source and processes.

I can provide several kinds of enterprise applications depending on your organization's needs:

Desktop Application with a shared data source

This application is just like a desktop application except that it does not use a local database. Instead, it uses a database that resides on a network server: an enterprise database.

Distributed Application with a shared data source

A distributed application is designed so that the processing is shared across multiple machines. A typical distributed application might have the presentation layer of code run on the users machine, and the business and data code run on a network server. One of many advantages to this design is that the application will perform in a consistent manner for all users whether or not they have a fast or slow computer. The datasource will generally be an enterprise database.

Distributed Model-View-Controller (MVC) Application with a shared data source

I won't go into the complexities of the MVC design pattern, but I will explain two of the prime advantage for users:

  • Because the code is partitioned into pluggable components (models, views, and controllers), the application can have several different kinds of interfaces. The same application could be accessed through an html application (thin-client), desktop-style application (thick-client), a wireless device, or by another system (peer-to-peer)
  • The pattern allows the process on the server-side to talk to and update the presentation on the client-side (GUI) without a user gesture. A prime example of this pattern, or similar pattern, at work is some of the stock market programs that show live data with automatic, real-time updates. As the stock data changes, the server process pushes it to all the users that are logged in without the user having to do anything.

Web Application

Web Applications

Copyright © 2004 David Wilson-Burns