Select A Section home public service database mgr. data access data modeler site notes |
Currently In This Section Public Service Computer Science Research ( Please Scroll Down ) |
Section Pages date protocol comm. protocol theory research amateur science news |
This is a legally copyrighted work, __________________________________________________
__________________________________________________ Most of the following research took place between the turn of the century and 2015, when major AxleBase work was stopped. All theory, research, system engineering, documentation, and web site maintenance presented here was done by one man.
The questions and postulates that gave rise to AxleBase seemed like foolish, unbelievable, and even embarrassing fantasies when first imagined; initialy so fantastic that they were not even shared with friends. Although now an operational system that seems obvious, when the project began at the turn of the century, such a system was undreamed-of. The following questions and scientific postulates were developed over a period of years in the sequence shown as the AxleBase project progressed. The first three arose almost together near the turn of the century. Scientific Rigor :
Engineering :
Please enjoy the following with me.
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
__________________________________________________
_________________________ Postulate :
A simple proposition, but the fact that our civilization has poured hundreds of billions of dollars into developing the I.B.M., Oracle, Microsoft and open-source database managers made this simple proposition non-trivial. The task was strongly believed, even by the researcher, to be impossible. Finding : True. Proof :
Qualification :
Caveat :
Extensibility :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
Finding : True. Proof :
( Note :
This postulate was addressed concurrently with the previous and following postulates. Another way to state the finding is that the only meaningful measure of a computer language's power is, like any tool, the power that it delivers to the worker. High-Level :
Extensibility :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
Finding : True. Proof :
This was addressed concurrently with the previous two postulates. Extensibility :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
When postulated at the turn of the century, a table of a few gigabytes on a mainframe was considered large. Finding : True. Proof :
( Although simple internet search engines and data warehouses followed, they lack the power of relational database managers.) Extensibility :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
When postulated at the turn of the century, a personal computer disk drive with capacity of more than a gigabyte was unusual. Finding : True. Proof :
Extensibility :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
Using AxleBase for proof added confounding requirements :
Finding : True. Proof :
Observation :
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
_________________________ Postulate :
Using AxleBase for proof added confounding requirements :
Compared to the others, this postulate was especially daunting. There was no conceivable route to a proof at the time. It was easy to imagine solution by a huge organization, but not by one man. Finding : True. Proof :
( The solution was found within a highly abstracted conceptual plane making the elegantly simple solution appear more sophisticated than it is. See the following Unexpected Findings section.)
End of the Postulates And Findings Section. Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
__________________________________________________ Computing Power A totally unexpected finding from all the work was possibly the greatest; i.e., that considered software engineering can overcome hardware shortcomings. A factor in this research that is obscured by the mass market and the mass marketers is the fact that the sophisticated AxleBase system will run just fine on a turn-of-the-century desktop computer. His development was, and in 2014 still is, done entirely on a Windows 98 computer with a four gig hard drive. His test machines included Windows 95 and an even older Windows NT machine until they finally died. A result of that finding is the indication that software engineering in business and academia has been a farce. This is especially true considering the fine tools available and the billions available for funding. Software Engineering Impact The Google corporation was understandably proud of the speed of their Dremel database manager. But Google relied upon massive amounts of hardware for that speed, whereas the AxleBase code was laboriously designed and engineered for power. A comparison revealed that AxleBase was over four thousand times faster than the Google system due entirely to software engineering. (See Performance Comparisons : Dremel on the performance page.) Unexpected Benefits It was found that care in engineering and coding frequently point to, and offer unexpected support for, additional design features. Features that are real and not superfluous "bloatware".
Solution Simplicity The project required a great deal of time and thought because it was original research and because of its massive size, but it was found that many solutions within it are far simpler than expected. The alterations of hardware characteristics, in particular, appear far more complex than they are in actuality because the complexity lies within a highly abstracted conceptual plane where the solutions were found, investigated, simplified, and then brought back down to the implementation level. ( This simplicity section and the Problem Domain section do not conflict because different domain abstractions are addressed therein.) Engineering Foundations Software engineering was found to have extremely important basic principles that are not necessarily intuitive. Simplicity is an example. This researcher frequently interrupted work to return to supporting systems to simplify them. The effort delivered several tangible benefits, but most importantly for the researcher was that the beautiful simplicity enhanced the assessment of structural efficacy and also freed the mind to build more complex structures atop the simplified base; probably understandable by engineers in many disciplines.
Click to return to table of contents at the top. Or press {Alt Left Arrow} to return to previous text.
__________________________________________________ |
Web site and technology |
||
Web site is maintained with Notepad.
|