Skip Links

Q&A: Why Union Bank scrapped AIX for Red Hat

Web infrastructure upgrade led to financial institution’s broad-scale Linux commitment

By Jennifer Mears, Network World
February 21, 2007 03:46 PM ET
  • Print

As Linux establishes itself as a mainstream operating system, and open source tools and applications prove their enterprise readiness, a growing number of organizations are talking publicly about their open source deployments and direction. Recently, Mok Choe, CTO at Union Bank in Monterrey Park, Calif., spoke with Network World Senior Editor Jennifer Mears about the financial institution’s decision to scrap proprietary Unix systems for commodity servers running Red Hat Linux. Here is an edited transcript of their conversation:

Getting personal:Mok Choe

Title: CTO
Organization: Union Bank of California
Responsibilities: Promoting the use and development of emerging technologies at Union Bank in the areas of infrastructure (hardware, operating systems, network and telephone), applications architecture, information management and data warehouse architecture.
Time on job: A little more than a year
Previous jobs: CIO, DoubleClick; Co-CIO, Ameritrade
Company size: One of the 25 largest commercial banks in the country with more than 320 branch offices and 10,000 employees.
Open source experience: In previous jobs Choe worked with FreeBSD, Linux, JBoss TomCat, Apache, CVS (version control software) and application development framework Jakarta Struts.
Fun fact: Ran a few marathons.
Click to see: Mok Choe's bio

Give me some background on your move to Linux and open source.

We were faced with having to do an upgrade of our Web infrastructure last year, which gave us an opportunity to really look at our architectural direction. We decided to head in the direction of horizontal scaling using commodity hardware and open source tools. There are multiple drivers behind this thing. Cost is clearly one of them. First and foremost always is the reliability and performance. The second thing is we wanted to be able to scale much easier than we do today. Since we run on big boxes, at some point to scale you have to buy another big box. Instead of that, we wanted to be able to rapidly manage capacity by adding or subtracting commodity hardware.

Had you been using any open source software previously?

On a smaller scale, a Linux deployment did exist, but in very small, departmental solutions.

How did you decide that it was time to look at a broader deployment of Linux and open source?

That was part of the overall architectural direction that we decided upon for our Web applications. From the enterprise perspective, it was a big decision. Going with the commodity hardware was a big decision. Going with open source was a big decision.

So you determined that open source had reached a point that you felt comfortable bringing it into larger production environments?

Yes, we have a number of people who have had experience with Linux, including myself in my previous job, so we were rather comfortable going with that decision. We did make sure that we are meeting all the compliance requirements, so both internal and external regulatory bodies were consulted.

How did you go about that?

Since we are going the open source route, everything must be open, so to speak. All the documentation that’s required has been satisfied, and we have an internal arm auditing our use of open source tools.

  • Print
What is Tech Briefcase?
TechBriefcase is a new, free service where IT Professionals can Search, Store and Share IT white papers and content like this. Learn more
Bookmark content
Speed up your research efforts with content across the web.
Search and Store
Find the white papers you need. Create folders for any topic.
View Anywhere
Open your briefcase on your iPhone, tablet or desktop. Share with colleagues.
Don't have an account yet?

Videos

rssRss Feed