The design does not scale well to multiple CPUs. It stems from design decisions made to optimize the multi-threading version of InterBase on single CPU servers. That is not due to the operating system, as has been supposed by some people. If you are on a Superserver configuration, the current InterBase design will not help you to benefit from using multiple CPUs. This is a very high level view of the hardware configuration to give you ideas on how to set a system up with the sort of reliability we are addressing here. If this isn't self-explanatory, do a MAN or INFO lookup on 'Murphy' and 'entropy'. No matter how well you plan, you will have problems. If you fail to design it right the first time, you will end up doing three times the work when faced with the problems of your poorly thought-out design. It is my philosophy that time spent up front is time saved later. You want to be able to fix a problem in the least possible time. Hardware is cheap and is getting cheaper all the time.
Our decisions about the basic design approach and coding were based on these assumptions: With a proper database design, anyone can create a 24x7 system, regardless of the hardware, operating system or even the server software.Īs for the hardware design issue, failures will occur even with the most expensive systems money can buy. The first question a developer needs to ask is this: are the tools at hand versatile enough to create a solution that can handle all the identified requirements?īecause of a design approach that was radical at the time, InterBase is extremely well suited to a 24x7 configuration, as long as the developer understands the server and the tools available. This means that a developer has to really analyse requirements and design the best solution for his own installation. Vendors make tradeoffs in order to satisfy the largest target market. The truth is, no software or hardware vendor could create a package that would begin to approach the particular needs of any one installation. Many people have seen the term '24x7' - a shorthand label for 'a requirement to keep database available at all times' - and think that the solution will be found on either the database software or the hardware platform. We all benefit and your overall karma will be improved. If, after reading this, a few of you come up with better ways to accomplish the same thing, SHARE THE IDEAS. I identify some common situations that you might face and show how we approached the solutions. Please don't look upon this as the only approach to all problems. Dalton Calford shares his real-life solutions to some implementation problems
0 kommentar(er)
