A grand tour of Oracle Exadata, Part 1
Pythian has full-featured Oracle Exadata Services complete with successful implementations and reference customers.
When Oracle first introduced Exadata at OpenWorld 2008, it was aimed squarely at the data warehouse market dominated by Teradata, Netezza, and other pure-play vendors. Version 2, introduced a year later, has expanded the scope to include general-purpose mixed and even pure transaction processing workloads. Marketing claims abound with reports of 10x and faster speed improvements.
In this series of articles (part 2 here and part 3 here), we’ll explore the major components of Exadata and the Oracle Database Machine and take a peek at how they’re designed with performance and scalability in mind.
Going against the industry trend of embedding database-specific logic in hardware, Exadata makes use of commodity off-the-shelf hardware components, with an underlying open source operating system stack. While arguably such a common hardware architecture makes it easier for competitors to copy functionality, it also gives Exadata a well-understood, stable, and tested platform that’s constantly evolving higher speeds and capacities.
Database nodes
The database nodes in an Oracle Database Machine will be familiar to anyone who has worked with Oracle RAC in a Linux/x86 platform. They consist of exactly the same Sun Fire x4170 1U servers sold for general-purpose computing, but come maxed out in terms of configuration: Read the rest of this entry . . .
