Design Guidelines

XML suffers from an all too common problem with new technologies—”buzzworditis.” Like the Java and multitiered—or was it “n-tiered”—architectures before that, XML has visibility at the executive level—the nontechnical executive level. This visibility leads to corporate edicts and wondering why the entire system has not been converted to XML. However, like Java and other architectures, XML isn’t an answer in and of itself; it’s simply a tool you can use to help build your technical solution. We recommend the following six general design guidelines for the judicious use of XML in the data architecture of your systems.

If You Don’t Need It, Don’t Use It

One thing many architects do not initially see when using XML is that it ...

Get Borland® JBuilder™ Developer’s Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.