By Acshorten-Oracle on Nov 13, 2008
At the moment I am in the middle of writing a guide to choosing the hardware architectures for our product line. One of the ideas I am playing with at the moment is boiling the factors that go into the decision into their raw levels.
A couple of years ago I attended some Project Management training and the discussion was around the "Project Management Triangle". A balanced plan requires that time, cost and quality are all in balance. If you "unblance" the triangle you can risk the project to be delayed, not meet the requirements or be cancelled altogether.
When deciding the factors for choosing architecture I came up with a similar concept. I call it the "Architectural Triangle". The dimensions in this triangle are availability, performance and maintainability. The diagram below shows both "triangles"
Availability is the measure of how available the system is against negotiated availability time (this includes Disaster Recovery). Performance is the measure of speed and some sense of size. Maintainability is the measure of skills, resources and costs associated with your site and the solution.
Just like the project management one, if you unbalance this one you can choose a hardware architecture that is really not suitable for your site.
The guidelines I am writing will take each of the basic variations of the architecture and outline the merits of each to assist customers and partners in making the right decision.