CA Meets IT, Integration Challenges (Continued)
How to Decide on Java vs. .NET?
Carter: You mentioned Java vs. .NET—obviously, you guys support both camps there, but internally when you guys are building and deploying your own applications, how do you make the decision about which route to take?
LeClair: We don't have a formal standard where "everything will be Java." I think we take a realistic attitude and look at what we're extending. So, if you're extending an existing product that has a strong Microsoft affinity—you know, the whole product runs on Windows—then, naturally we continue to extend that in .NET. If it's something we need to deploy on multiple platforms, we'll be inclined to do it in Java.
Carter: What kinds of developments do you see impacting the way you do your job in the upcoming year or two?
LeClair:. I think that the general heading of utility computing—or "computing on demand" as IBM likes to call it—is something where we're already far down the road at CA, and over the course of this calendar 2003, we're going to have some interesting new releases that will let you essentially have your systems be more significantly self-administrating and self-healing.
So, we'll be able to have a distributed environment where we have a stack of servers running one of our specific applications, another stack running another one, and based on the service level, we'll be able to dynamically reassign or reconfigure the network to make sure we're delivering the right capacity to the right system. This will be great for us from an IT perspective in giving us flexibility in how we deploy that, and it will be a positive thing for our customers as far as managing their environments as well.
Back to top
|
Integration Insanity 
