Linux in the cloud (Ubuntu 10.04 vs RHEL 5.4)

-
vs

I recently did a comparison between Ubuntu 10.04 and RHEL 5.4 to determine what our standard server install should be. Just to be honest, windows server started out to be in the mix but was quickly disregarded as it really doesn't lend itself to scaling out in any reasonable manner. I set these up using the rackspace cloud which I have to say was a dream come true. I had both servers up and running j2ee application servers in less than 1 hour.

First off, I first used redhat back when it was shiny and new (94-95) and used it for quite some time afterward. I've also used a variety of other unix and/or linux systems (slackware, debian, ubuntu, suse, caldera, SCO, solaris, aix, hp-ux). That having been said, I am a linux USER, NOT a kernel hacker. So the inner workings are quite as important as much as getting a useful and reliable system together quickly.

What I discovered is that Redhat is trying to build a stable platform that doesn't change. They are committing the ultimate act of software suicide that IBM and Microsoft (and now even Apple) seem to have perfected in recent years. The fact is that Ubuntu has begun to figure out what makes things tick and they are iterating and evolving with the marketplace.

When I looked at the packages that were supported on the two platforms, everything on RHEL was at LEAST 3-4 years old and some of it was older. I understand from a business perspective, they think this makes sense because it costs money to innovate, but it is a serious problem. They are effectively ignoring 4 years of serious progress.

Ubuntu, on the other hand, was seriously up to date. Ubuntu 10.04 is current as of April and I know they will be release a new upgrade October. In addition, I have the flexibility to back/forward port new packages between releases if it becomes really necessary.

If you want outdated software that will work great as long as nothing in your business changes and you're OK being 4+ years behind everyone else, choose Redhat. If you want software that will evolve and change with your business over time, choose Ubuntu. If you want software that nobody will fire you for choosing, choose Microsoft (or IBM).

Comments

floatingboat said…
I am doing a similar comparison exercise for Ubuntu 10.04LTS and CentOS 5.4.

Can you share your evaluation criteria?
September 3, 2010 at 11:56 AM
Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa
Read more

The difference between Scalability, Performance, Efficiency, and Concurrency explained

-
I thought I'd give some explanation of the difference between scalability, performance, Efficiency, and concurrency. To make things more accessible (and because I'm watching a cooking show on TV) I'm going to use a baking metaphor to help explain the differences. In our case, the system in question is baking cookies for consumers. Scalability, is how well something responds to adding more resources. If we can double our capacity by doubling the number of resources, we've got linear scalability. In our baking example, if we add more ingredients, we can scale to a larger number of cookies. To contrast with our other metrics, this doesn't actually increase the performance of creating a single cookie (they still take 10 minutes to bake), and the efficiency is the same (we just have more capacity). We also cannot bake more cookies in a fixed time period, but over a larger time period we can produce more cookies. Performance is how fast something can get done, u
Read more