Sheesh guys...are you new to this game? Without exception, the customers I encounter are doing J2EE for webservices and .NET for the "Application" and "Presentation" layers for enterprise applications.
These are companies that have HUGE investments in UNIX enterprise servers (WebLogic, WebSphere, etc) and want some of the convenience that .NET provides to data presentation, re-use of their OO developers (Good thing...means they aren't running offshore for their dev needs) and easy implementation of webservices. I am speaking in the billions of records affected for a simple reporting query and in the multi-millions of records for update/insert/create query operations. Customer perception, right or wrong, is...UNIX = clusterable, scalable, reliable...Windows = not. Give .NET another six-months in production with high-capacity, mission-critical enterprise apps (specifically in finance and manufacturing), and then this benchmark will have value. Otherwise, no matter how many esoteric, theoretical, optimal benchmarks you provide, you will be shouting to deaf ears at the CIO, COT, and Architect levels. There are no "KO" scenarios in tech any longer...us CTO/Architects just don't do that any more...and even the MBMs (Manage-by-magazine) types who hold the purse strings have backed way, way off from the "Must have" technology pushes from four years ago...tech is a much different game these days, don't look for rapid, revolutionary change, but easy, calm evolution. Cheers, Jonathan C. Caffee Caffee Consulting [EMAIL PROTECTED] -----Original Message----- From: Chris [mailto:15seconds@;dracoassociates.com] Sent: Tuesday, October 29, 2002 11:56 AM To: ActiveServerPages Subject: RE: J2EE vs .NET Thanks Daniel, this is powerful stuff <SNIP> --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
