Application design

Joe,

At 11/26/02 01:23 AM, you wrote:

The beauty of this approach is that it can be implemented in any language,
including RPG.  While Java might lend itself a little more easily to the
interface definition, I've been playing around a little and it's actually
not too difficult to design the same sort of infrastructure with service
programs.  And once you've separated business logic from the data
deployment, it allows you to do some awesome things - like combine two
completely different databases seamlessly, or use both online and offline
storage, or mirror data to multiple formats, or provide transparent
logging - the list is endless.

 Can you give a real life application scenario (maybe order entry /
billing / inventory), specifying what functions would be taken care of in
which layer and what criteria would you use?

 -mark