XML: Too Much of a Good Thing
Software vendors may want you to think XML is essential for all kinds of development. Trouble is, it's not.
November 7, 2003
![Network Computing logo Network Computing logo](https://eu-images.contentstack.com/v3/assets/bltde8121fc52c5c8f3/blt3f3d0318f746b1c2/65a530e4187606040a1d8b8c/placeholder.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
CPU speeds have kept up with software bloat, but not by a lot. If we add too much bloat, we may wind up with unacceptably slow systems and users who are understandably irate.
So don't go the "everything XML" route until you're certain you can support it. Some jobs just don't require XML, and the XML processors I've seen aren't ready for near real-time and high-volume applications. Think about your application, think about your needs, and, most important, think about the benefits of XML versus the cost. Consider the impact on CPU, network bandwidth and disk storage before you move that data warehouse to XML.
You May Also Like
Maximizing cloud potential: Building and operating an effective Cloud Center of Excellence (CCoE)
September 10, 2024Radical Automation of ITSM
September 19, 2024Maximizing Manufacturing Efficiency with Real-Time Production Monitoring
September 25, 2024