Skip to main content

Caché Application and Data 2

In general, because the Caché Application and Data Servers are so well integrated, it's often unclear exactly where one ends and the other begins.

But there is one reason for separating the two, at least conceptually: Caché can connect with other database management systems. This enables all of the Web and object technology we're going to learn about in this tutorial to be used with other SQL systems, for example, from Oracle or Microsoft. In these situations Caché acts as the application server while the other database systems act as data servers.

It's also important to recognize that the diagram on the preceding page shows a logical configuration, not necessarily the physical computer configuration. In fact, all of these components (browser and web, application, and data servers) may be running on a single computer generated description: physicalservers1.gif. This is often the case during development. Or, Caché and the Web server could be sharing a computer generated description: physicalservers2.gif. Or, the Caché Application and Data Servers could share a computer separate from the Web servergenerated description: physicalservers3.gif. Or, the Caché Application Server and Web server could share a computer and the Caché Data Server run on a different computer generated description: physicalservers4.gif. Or, ... well you get the idea.


To continue with the next part of this tutorial, click here.

FeedbackOpens in a new tab