AnandTech 1.0

As most of you know, AnandTech started out as a static HTML site, hosted on GeoCities. Static driven sites are simply HTML based with the content contained within; dynamic driven sites fetch their content from external sources (usually database servers). Back then, static sites were quite popular while dynamic driven web sites were really just starting to catch on. In 1998, at Comdex, we laid out the first dynamic version of AnandTech.com. We decided on Oracle 8i as the database server, and ColdFusion 4.0.1 as the application server. We ran Oracle 8i and ColdFusion on two separate Sun Enterprise servers. We had no issues with Solaris or Oracle, performance-wise, but ColdFusion talking to Oracle was another story.

We developed a fairly simple content management solution that allowed us to post content through web forms. This approach to publishing saved a lot of time as content and the editorial staff grew. Articles could be posted from anywhere, and they could updated or removed at will by using our forms-based interface to the database. At that time, the content management engine was not feature-rich; it performed just the basic tasks necessary for the small editorial staff that we had.

The first version of the site was probably the most problematic version of the website (go figure), and the most difficult to maintain. Oracle is a powerful database server, without a doubt, but it lacks the finesse of Microsoft SQL Server and other database servers to some extent. The management UI leaves much to be desired (it doesn't hold a candle to SQL Server Enterprise Manager), and the language, although powerful, is not for everyone.

For ColdFusion to talk to Oracle, we had to use the Oracle Native drivers, which caused us a fair bit of grief and wasted time, as the SQL syntax had to be compatible with Oracle. When the development team consisted (and still consists) of one developer, time is critical. Speaking as the developer, I come from a SQL Server/Sybase world and while it isn't hard to pick up on Oracle's syntax, it is entirely too painful to use when time is so critical, especially when working with dates. Aside from the pain of the syntax, the native drivers also caused some anguish in ColdFusion. ColdFusion was crashing occasionally and caused some unnecessary administrative headaches that needed to be rectified each time it went down. By this time (about a year or less later), it was time to move on to something more stable.

Hardware used in version 1.0
Sun Enterprise 250 w/ 512MB Memory

View version 1.0 of the website

Index AnandTech 2.0 & 3.0
Comments Locked

67 Comments

View All Comments

  • Dennis Travis - Tuesday, July 27, 2004 - link

    Great Job with the site Jason as always and it was interesting to see how far things have come along since I first started visiting here.

    Keep up the great work.

    ...Dennis
  • stoneranger - Tuesday, July 27, 2004 - link

    kewl read, I enjoyed it. Really. I think it is very interesting the progress the industry has made. Things are actually getting easier. I love anand tech. Of course I could be considered a geek by some. But I think it is by far one of the best sites on the web.
  • Frozen7 - Tuesday, July 27, 2004 - link

  • Frozen7 - Tuesday, July 27, 2004 - link

  • Da3dalus - Monday, July 26, 2004 - link

    Nice to see some of the earlier designs, I didn't visit this place in the 1.0 to 3.0 days.
  • cameronj - Monday, July 26, 2004 - link

    Under the 5.0 heading it says "
    Hardware used in version 4.0
    5 x Dual AMD Athlon MP 1900+ w/ 1GB Memory"

    Interesting article though :)
  • CrystalBay - Monday, July 26, 2004 - link

    Ahh The Celery Report...Do you guys have all this stuff archived ?
  • CompMan86 - Monday, July 26, 2004 - link

    Two errors: 1) The second graph on the conclusion page, the caption says "the graph below" instead of "the graph above." Also, "SQL Sever/Sybase world and while" on page 2 should say Server, not sever. Minor mistakes, just thought I'd give you the heads up. Otherwise, awesome article!

    And in response to the target=_blank comment, you have no control over window size or window attributes (like toolbars) with that. target=_blank is good when linking to an external site, but if you want to have a customized popup, javascript IS the standard.
  • quanta - Monday, July 26, 2004 - link

    Why the site keep on using Javascript to open a new window when it can be done using 'target=_blank' attribiute? Is that Anandtech's idea of 'standard compliance'?
  • PorBleemo - Monday, July 26, 2004 - link

    Great job Jason! Always an interesting change to see site background like this...

Log in

Don't have an account? Sign up now