1 / 9

Oracle Database Architectures Are Extremely Complex, And Very Expensive.

The Snippet Engine (SnEn). Oracle Database Architectures Are Extremely Complex, And Very Expensive. All of Their Complexity Goes Away ! The Snippet Engine Network Architectures Are Very Simple, Cheaper, and Much Faster. The Snippet Engine Uses CPU-Threads as SnEn Nodes

dorit
Télécharger la présentation

Oracle Database Architectures Are Extremely Complex, And Very Expensive.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Snippet Engine (SnEn) Oracle Database Architectures Are Extremely Complex, And Very Expensive. All of Their Complexity Goes Away ! The Snippet Engine Network Architectures Are Very Simple, Cheaper, and Much Faster. The Snippet Engine Uses CPU-Threads as SnEn Nodes That Act Like “Cyber Ants”. Thousands of Them, Each Working Autonomously and Together Forming a Very Powerful Worldwide Network

  2. All of This Complexity Goes Away !

  3. RAIDs RAIDs SnEn Database Server SnEn Database Server SnEn Database Server CPUs / Cores CPUs / Cores CPUs / Cores SnEn Architecture Is Based On Modern Computers, With a Very Simple Configuration Optional Home Computers Laptops Optional Nodes Nodes Nodes In Real-Time: Each Node will duplicate its portion of the Database to other Nodes, running anywhere in the world. This means that each Database Table is instantaneously duplicated on other Servers. Each duplicate is a “hot backup”, so that if one Server should fail, another Server instantaneously steps in. Nodes are “Cyber Ants” are CPU-Threads They are always “Alive” They are always “Talking” They are always “Thinking Ahead”

  4. Database Elements and Tables Database Elements and Tables SnEn Database Server Node Node Node Code Code Code Database Elements and Tables SnEn Isolates Database Elements By Its Design SnEn Database Servers SnEn Database Servers Oracle Overhead and Code Oracle Database Server Oracle Database Server Oracle Database Server SnEn: The Database Elements are automatically protected against multiple Servers concurrently using them. The Database Tables are spread across the Servers (not disks). Thus, each Node completely isolates its portion of the Database. Each Table is managed by its own code, executing at the lowest level. There is no overhead ! The Database is managed by its own code, that always executes as a Core-Thread, and cannot be interrupted. Thus, all Data Elements are automatically isolated for concurrent access. ORACLE: The Database Elements are not protected against multiple Servers concurrently using them. The Database Tables are spread across multiple Disks. This means that Oracle must insert software and overhead to manage the concurrent access. Thus, Data Elements are “forced” into isolation for concurrent access.

  5. SnEn Servers SnEn Server SnEn Servers Cyber Ant Cyber Ant Cyber Ant Cyber Ant Cyber Ant Cyber Ant Cyber Ant Cyber Ant Cyber Ant Code Code Code Code Code Code Code Code Code Data Table Data Table Data Table Snippet Engine’s Cyber Ants Website Hosting PHP Command and Data Packets Located Anywhere Manages Cyber Ant Objects Cyber Ants Are “Self-Aware” Objects Doing What They Know How To Do Data Table Data Table Key-Value Database Tables Data Duplicated To Others Located Far Away Located Anywhere Data Table Data Table Data Table Data Table SnEn Servers Running On Normal Desktops, Laptops, and Home Computers

  6. SnEn Server SnEn Server SnEn Database Servers Node Node Node Code Code Code SnEn Application Server Database Elements and Tables Appl 1 Appl 2 Appl 3 Nodes Nodes Nodes Data of the Applications Any Node Talks To Any Node Any Node can talk to any other Node, running on any computer in the world. Creating interacting applications that share synchronized data and capabilities is very easy, as this is part of the SnEn design. Internet Internet Nodes can send and receive Commands and Data with other Nodes running anywhere in the world. Applications on different computers can instantaneously synchronize and augment their Command and Control capabilities. Users Nodes ensure that the Data they manage is duplicated to other Servers. This is done directly, Node to Node, and in real-time. If any Server fails, another Server instantaneously steps in. A User never even knows the failure happened. Nodes are always “Alive”. They schedule themselves to “Think Ahead”. They have their own Command Queue, and execute as a Core-Thread so they cannot be interrupted.

  7. The Snippet Engine And Websites User’s Computer User’s Browser Standard Client-Side Browser Optional Standard Internet (Encrypted XML) Client-side JavaScript Optional Client-side Encryption Optional Standard Internet Directly to SnEn without using a Browser Standard Internet Website’s Hosting Server Website’s Server Environment Optional PHP Interacts with MySql Server Gets Request From Browser SnEn Database Server Server Gives Request to PHP PHP Interacts With Its Database CPU Thread Node Cyber Ant PHP Interacts With SnEn Servers SnEn Returns Everything Needed Even Complex Computations PHP Interacts with local and remote “Cyber Ants” Code Server Sends HTML to Browser Nodes Are The Database Essential for Mission Control, Networked Games, and Robotics: Each Node Can Send Commands and Data Directly To Other Nodes Running Anywhere In The World. This Makes Applications “Infinite”, As Thousands of Cyber Ants Interact To Synchronize and Aggregate Their Capabilities

  8. SnEn Server SnEn Server SnEn Server SnEn Server SnEn Server SnEn Servers Are Placed Anywhere In The World Database Tables Are Duplicated On Servers Running Anywhere In The World. If one part of the world has a power failure, other Servers are not effected. Thus, each Table always has a “hot backup”, and the Network never has any downtime.

  9. Nodes which manage Database Tables, are intelligently spread across the Network’s SnEn Servers Nodes Manage The Database Tables Each Browser, via the Hosting PHP code, effectively communicates directly with any Node in the worldwide Network. This is the same as saying that each Database Table interaction is automatically distributed to a specific Server for very fast processing. The Database Tables are each managed by a specific Server, and by a specific Node on that Server. Each Table is automatically duplicated to other Servers for “hot backup”. In this diagram of 36 Servers, each Database interaction is automatically directed to the Server managing that Table. This means that there are no “Database Bottle Necks”, and no “Single Point of Failures”. This simple Architecture is much faster than the Oracle Architecture. If a Server fails, another Server instantaneously steps in. The User never even knows it happened.

More Related